what_do_we_need_to_have_in_place_prior_to_initial_scrum_team_training
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
what_do_we_need_to_have_in_place_prior_to_initial_scrum_team_training [2015/11/20 07:30] – hpsamios | what_do_we_need_to_have_in_place_prior_to_initial_scrum_team_training [2020/06/04 10:40] (current) – Removed LINKBACK hans | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== What Do We Need to Have in Place Prior to " | ====== What Do We Need to Have in Place Prior to " | ||
- | ====== Premise ====== | ||
One approach you can take when going through initial Scrum / agile team training is to set yourself up for real work so that the very next day after you have gone through the training, you are operating in a Scrum / agile mode, actually doing it. There are huge benefits in doing it this way in that the training becomes a whole lot less theoretical, | One approach you can take when going through initial Scrum / agile team training is to set yourself up for real work so that the very next day after you have gone through the training, you are operating in a Scrum / agile mode, actually doing it. There are huge benefits in doing it this way in that the training becomes a whole lot less theoretical, | ||
+ | |||
+ | This is also what we'd do if, for example, an organization wanted to set up a pilot project to try out Agile and Scrum concepts and to understand how they'd be applied to their organization. | ||
====== Pre-Work ====== | ====== Pre-Work ====== | ||
Line 21: | Line 22: | ||
* Prepare a starting requirements list. This means having a list of high priority items that the Team could implement in the first Sprint / Iteration (say 2 to 4 weeks of work). Product Owners typically do this by getting with the technical lead and walking through a priority list getting at least an initial gauge of what can fit in the first Sprint / Iteration. The requirements need to be broken down so that a number of these can be worked on by the team in the first Sprint / Iteration, not just one. The idea here is not to be perfect – the Product Owner will work with the Team on these requirements during the training – but we need a starting point. We will need to get these printed on a 5x3 sized index cards so we can go through the planning exercises. | * Prepare a starting requirements list. This means having a list of high priority items that the Team could implement in the first Sprint / Iteration (say 2 to 4 weeks of work). Product Owners typically do this by getting with the technical lead and walking through a priority list getting at least an initial gauge of what can fit in the first Sprint / Iteration. The requirements need to be broken down so that a number of these can be worked on by the team in the first Sprint / Iteration, not just one. The idea here is not to be perfect – the Product Owner will work with the Team on these requirements during the training – but we need a starting point. We will need to get these printed on a 5x3 sized index cards so we can go through the planning exercises. | ||
* To have thought about the goals for the Team over the next 6-12 months so that you can articulate them to the Team. | * To have thought about the goals for the Team over the next 6-12 months so that you can articulate them to the Team. | ||
+ | |||
+ | {{tag> | ||
+ | |||
+ |
/home/hpsamios/hanssamios.com/dokuwiki/data/pages/what_do_we_need_to_have_in_place_prior_to_initial_scrum_team_training.txt · Last modified: 2020/06/04 10:40 by hans