Changes for page Planning Game

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -36,10 +36,10 @@
36	36	* For subsequent iterations, the team expects the velocity of the current iteration to be the same as the velocity of the previous iteration, as this is the best guess.
37	37	* Stakeholders select cards from the top of the story deck so that the sum of the points of all the selected cards matches the expected velocity. The stories on these selected cards will be implemented in the iteration. Remember that some stories may depend on other stories that need to be implemented first.
38	38	* **Story Deck Evolution**
39		- * Solved stories are removed from the Story Deck. As the project progresses, new usage requirements may emerge and be added as new cards to the Story Deck. Stories could also split or merge.
40		- * Estimated effort and business value are affected by the evolution of the project. Therefore, stories need to be re-evaluated and the story deck re-ordered on a regular basis, i.e. in the IPMs.
41		- * There may be stories that do not currently have a favorable ROI and are not worth implementing. They remain in the story deck because there is a chance that their estimated effort and business value will change over time, making them worth implementing later. Conversely, some stories may become irrelevant over time.
42		- * If the story deck has no stories with a ROI that makes them worth implementing, the project ends.
	39	+ * **Stories Evolve**: Solved stories are removed from the Story Deck. As the project progresses, new usage requirements may emerge and be added as new cards to the Story Deck. Stories could also split or merge.
	40	+ * **Estimates Evolve**: Estimated effort and business value are affected by the evolution of the project. Therefore, stories need to be re-evaluated and the story deck re-ordered on a regular basis, i.e. in the IPMs.
	41	+ * **Keep All Stories in the Deck**: There may be stories that do not currently have a favorable ROI and are not worth implementing. They remain in the story deck because there is a chance that their estimated effort and business value will change over time, making them worth implementing later. Conversely, some stories may become irrelevant over time as their estimated ROI decreases.
	42	+ * **Project End**: If the story deck has no stories with a ROI that makes them worth implementing, the project ends.
43	43
44	44	### During Iteration
45	45