https://agileme.wiki/wiki/api.php?action=feedcontributions&feedformat=atom&user=Mmusij 2026-06-14T19:21:33Z User contributions MediaWiki 1.38.6 https://agileme.wiki/wiki/index.php?title=File:Scrum_Framework_Shapes.pdf&diff=1663 2023-08-08T05:57:29Z

<p>Mmusij: Mmusij uploaded a new version of File:Scrum Framework Shapes.pdf</p> <hr /> <div></div>

Mmusij https://agileme.wiki/wiki/index.php?title=Build_Your_Agile_Flow&diff=1662 2023-07-06T06:20:42Z

<p>Mmusij: /* Materials */</p> <hr /> <div>[[Category:Agile:Workshops]][[Category:Agile]]<br /> ==Introduction==<br /> This exercise is related to [[Build Your Scrum Framework]] and allows leaders to build a diagram of a proposed Agile ecosystem for discussion. <br /> <br /> The workshop structure is based upon the 4 C’s framework described in Sharon Bowman’s Training From The Back of The Room (2009) (Bowman 2009).<br /> <br /> ==Learning Objectives==<br /> * Understand how an Agile ecosystem would exist in their organisation and gives rise to discussions about particular aspects<br /> <br /> ==Materials==<br /> &lt;pdf width=&quot;300&quot; height=&quot;500&quot;&gt;File:BYO_Agile_Flow.pdf&lt;/pdf&gt;<br /> <br /> ===In-Person===<br /> * Printed [[Media:BYO_Agile_Flow.pdf|Agile Flow shapes]] 1 per group<br /> * Flip chart paper, 1 for each table group<br /> * Blu-tac or similar for sticking to the walls<br /> * Scissors<br /> <br /> ===Distributed Online Working===<br /> * [[Media:BYO_Agile_Flow_individual_shapes.pdf|Agile Flow individual shapes]] that can be used in collaborative infinite canvas boards or similar<br /> <br /> ==Workshop Flow==<br /> ===Connections (5 Minutes)===<br /> # Start by asking the attendees to split into table groups of 4 and to acquire the necessary materials to start for each table group.<br /> <br /> ===Concepts (10 Minutes)===<br /> # Introduce the printed materials and have a brief discussion on the various items and what they stand for.<br /> <br /> ===Concrete Practice (25 Minutes)===<br /> # Ask the attendees to construct their respective Agile flow diagram on a sheet of flip chart paper.<br /> <br /> ===Conclusions (15 Minutes)===<br /> # Conclude with a show and tell with each table group presenting their posters to the attendees<br /> # Facilitate any questions with the models<br /> # Finish up with a team share back to discuss their models<br /> <br /> ==References==<br /> * Training From The Back of The Room, Sharon L. Bowman, Pfeiffer, 2009<br /> * https://weisbart.com/byos, Adam Weisbart, accessed 2018<br /> <br /> ==See Also==<br /> * [[Build Your Scrum Framework]]<br /> * [[Build Your Kanban Framework]]</div>

Mmusij https://agileme.wiki/wiki/index.php?title=Build_Your_Agile_Flow&diff=1661 2023-07-06T06:19:41Z

<p>Mmusij: /* Materials */</p> <hr /> <div>[[Category:Agile:Workshops]][[Category:Agile]]<br /> ==Introduction==<br /> This exercise is related to [[Build Your Scrum Framework]] and allows leaders to build a diagram of a proposed Agile ecosystem for discussion. <br /> <br /> The workshop structure is based upon the 4 C’s framework described in Sharon Bowman’s Training From The Back of The Room (2009) (Bowman 2009).<br /> <br /> ==Learning Objectives==<br /> * Understand how an Agile ecosystem would exist in their organisation and gives rise to discussions about particular aspects<br /> <br /> ==Materials==<br /> ===In-Person===<br /> * Printed [[Media:BYO_Agile_Flow.pdf|Agile Flow shapes]] 1 per group<br /> * Flip chart paper, 1 for each table group<br /> * Blu-tac or similar for sticking to the walls<br /> * Scissors<br /> <br /> &lt;pdf width=&quot;300&quot; height=&quot;500&quot;&gt;File:BYO_Agile_Flow.pdf&lt;/pdf&gt;<br /> <br /> ===Distributed Online Working===<br /> * [[Media:BYO_Agile_Flow_individual_shapes.pdf|Agile Flow individual shapes]] that can be used in collaborative infinite canvas boards or similar<br /> <br /> ==Workshop Flow==<br /> ===Connections (5 Minutes)===<br /> # Start by asking the attendees to split into table groups of 4 and to acquire the necessary materials to start for each table group.<br /> <br /> ===Concepts (10 Minutes)===<br /> # Introduce the printed materials and have a brief discussion on the various items and what they stand for.<br /> <br /> ===Concrete Practice (25 Minutes)===<br /> # Ask the attendees to construct their respective Agile flow diagram on a sheet of flip chart paper.<br /> <br /> ===Conclusions (15 Minutes)===<br /> # Conclude with a show and tell with each table group presenting their posters to the attendees<br /> # Facilitate any questions with the models<br /> # Finish up with a team share back to discuss their models<br /> <br /> ==References==<br /> * Training From The Back of The Room, Sharon L. Bowman, Pfeiffer, 2009<br /> * https://weisbart.com/byos, Adam Weisbart, accessed 2018<br /> <br /> ==See Also==<br /> * [[Build Your Scrum Framework]]<br /> * [[Build Your Kanban Framework]]</div>

Mmusij https://agileme.wiki/wiki/index.php?title=File:BYO_Agile_Flow_individual_shapes.pdf&diff=1660 2023-07-06T06:18:41Z

<p>Mmusij: </p> <hr /> <div></div>

Mmusij https://agileme.wiki/wiki/index.php?title=File:Agile_culture.jpg&diff=1659 2023-07-06T06:13:28Z

<p>Mmusij: Uploaded with SimpleBatchUpload</p> <hr /> <div></div>

Mmusij https://agileme.wiki/wiki/index.php?title=File:Agile_metrics.jpg&diff=1658 2023-07-06T06:13:28Z

<p>Mmusij: Uploaded with SimpleBatchUpload</p> <hr /> <div></div>

Mmusij https://agileme.wiki/wiki/index.php?title=File:Agile_process.jpg&diff=1657 2023-07-06T06:13:27Z

<p>Mmusij: Uploaded with SimpleBatchUpload</p> <hr /> <div></div>

Mmusij https://agileme.wiki/wiki/index.php?title=File:Agile_teams.jpg&diff=1656 2023-07-06T06:13:27Z

<p>Mmusij: Uploaded with SimpleBatchUpload</p> <hr /> <div></div>

Mmusij https://agileme.wiki/wiki/index.php?title=File:Alignment.jpg&diff=1655 2023-07-06T06:13:27Z

<p>Mmusij: Uploaded with SimpleBatchUpload</p> <hr /> <div></div>

Mmusij https://agileme.wiki/wiki/index.php?title=File:Autonomy.jpg&diff=1654 2023-07-06T06:13:26Z

<p>Mmusij: Uploaded with SimpleBatchUpload</p> <hr /> <div></div>

Mmusij https://agileme.wiki/wiki/index.php?title=File:Blockers.jpg&diff=1653 2023-07-06T06:13:26Z

<p>Mmusij: Uploaded with SimpleBatchUpload</p> <hr /> <div></div>

Mmusij https://agileme.wiki/wiki/index.php?title=File:Budget.jpg&diff=1652 2023-07-06T06:13:26Z

<p>Mmusij: Uploaded with SimpleBatchUpload</p> <hr /> <div></div>

Mmusij https://agileme.wiki/wiki/index.php?title=File:Compliance.jpg&diff=1651 2023-07-06T06:13:25Z

<p>Mmusij: Uploaded with SimpleBatchUpload</p> <hr /> <div></div>

Mmusij https://agileme.wiki/wiki/index.php?title=File:Cross_functional_teams.jpg&diff=1650 2023-07-06T06:13:25Z

<p>Mmusij: Uploaded with SimpleBatchUpload</p> <hr /> <div></div>

Mmusij https://agileme.wiki/wiki/index.php?title=File:Customer_feedback.jpg&diff=1649 2023-07-06T06:13:24Z

<p>Mmusij: Uploaded with SimpleBatchUpload</p> <hr /> <div></div>

Mmusij https://agileme.wiki/wiki/index.php?title=File:Empiricism.jpg&diff=1648 2023-07-06T06:13:24Z

<p>Mmusij: Uploaded with SimpleBatchUpload</p> <hr /> <div></div>

Mmusij https://agileme.wiki/wiki/index.php?title=File:Experimentation.jpg&diff=1647 2023-07-06T06:13:24Z

<p>Mmusij: Uploaded with SimpleBatchUpload</p> <hr /> <div></div>

Mmusij https://agileme.wiki/wiki/index.php?title=File:Funding.jpg&diff=1646 2023-07-06T06:13:23Z

<p>Mmusij: Uploaded with SimpleBatchUpload</p> <hr /> <div></div>

Mmusij https://agileme.wiki/wiki/index.php?title=File:Governance.jpg&diff=1645 2023-07-06T06:13:23Z

<p>Mmusij: Uploaded with SimpleBatchUpload</p> <hr /> <div></div>

Mmusij https://agileme.wiki/wiki/index.php?title=File:Managing_capacity.jpg&diff=1644 2023-07-06T06:13:23Z

<p>Mmusij: Uploaded with SimpleBatchUpload</p> <hr /> <div></div>

Mmusij https://agileme.wiki/wiki/index.php?title=File:Outcomes.jpg&diff=1643 2023-07-06T06:13:22Z

<p>Mmusij: Uploaded with SimpleBatchUpload</p> <hr /> <div></div>

Mmusij https://agileme.wiki/wiki/index.php?title=File:Product_-_service.jpg&diff=1642 2023-07-06T06:13:22Z

<p>Mmusij: Uploaded with SimpleBatchUpload</p> <hr /> <div></div>

Mmusij https://agileme.wiki/wiki/index.php?title=File:Reflective_practice.jpg&diff=1641 2023-07-06T06:13:22Z

<p>Mmusij: Uploaded with SimpleBatchUpload</p> <hr /> <div></div>

Mmusij https://agileme.wiki/wiki/index.php?title=File:Risk_issues_dependencies.jpg&diff=1640 2023-07-06T06:13:22Z

<p>Mmusij: Uploaded with SimpleBatchUpload</p> <hr /> <div></div>

Mmusij https://agileme.wiki/wiki/index.php?title=File:Self_org_teams.jpg&diff=1639 2023-07-06T06:13:21Z

<p>Mmusij: Uploaded with SimpleBatchUpload</p> <hr /> <div></div>

Mmusij https://agileme.wiki/wiki/index.php?title=File:Strategy.jpg&diff=1638 2023-07-06T06:13:21Z

<p>Mmusij: Uploaded with SimpleBatchUpload</p> <hr /> <div></div>

Mmusij https://agileme.wiki/wiki/index.php?title=File:Value.jpg&diff=1637 2023-07-06T06:13:21Z

<p>Mmusij: Uploaded with SimpleBatchUpload</p> <hr /> <div></div>

Mmusij https://agileme.wiki/wiki/index.php?title=File:Vision.jpg&diff=1636 2023-07-06T06:13:04Z

<p>Mmusij: Uploaded with SimpleBatchUpload</p> <hr /> <div></div>

Mmusij https://agileme.wiki/wiki/index.php?title=File:BYO_Agile_Flow.pdf&diff=1635 2023-07-05T09:34:19Z

<p>Mmusij: Mmusij uploaded a new version of File:BYO Agile Flow.pdf</p> <hr /> <div></div>

Mmusij https://agileme.wiki/wiki/index.php?title=Build_Your_Kanban_Framework&diff=1634 2023-06-30T00:27:14Z

<p>Mmusij: /* Workshop Flow */</p> <hr /> <div>[[Category:Agile:Workshops]][[Category:Agile]]<br /> ==Introduction==<br /> This exercise is related to [[Build Your Scrum Framework]] and allows attendees to have a go at building a diagram of the [[Kanban Framework]]. The workshop structure is based upon the 4 C’s framework described in Sharon Bowman’s Training From The Back of The Room (2009) (Bowman 2009).<br /> <br /> ==Learning Objectives==<br /> * Begin to understand how the Kanban framework fits with events, roles and artefacts<br /> <br /> ==Materials==<br /> * Copies of the [[Media:Kanban_Framework.jpg|Kanban poster]], 1 per group<br /> <br /> ===If Using Tactile &amp; Physical Media For Training===<br /> * Printed [[Media:Kanban_Framework_Shapes.pdf|framework shapes]] 1 per group<br /> * Printed [[Media:Scrum_Framework_Arrows.pdf|arrows]] 1 per group<br /> * Flip chart paper, 1 for each table group<br /> * Blu-tac or similar for sticking to the walls<br /> * Scissors<br /> <br /> ===If Using Electronic Distributed Training===<br /> * [[Media:Build_Your_Kanban_-_For_Distributed.pptx|PowerPoint Presentation]] by Stuart Bargon with the shapes as movable objects<br /> ** Instead of using the cut outs and flip chart paper, try hosting the presentation in design mode whilst sharing the screen with a video conference tool<br /> ** Now the teams can take control of the screen and move the shapes around to design their model<br /> <br /> &lt;pdf width=&quot;300&quot; height=&quot;500&quot;&gt;File:Kanban_Framework_Shapes.pdf&lt;/pdf&gt;<br /> <br /> ==Workshop Flow==<br /> ===Connections (5 Minutes)===<br /> # Start by asking the attendees to split into table groups of 4 and to acquire the necessary materials to start for each table group.<br /> <br /> ===Concepts (10 Minutes)===<br /> # Introduce the reading materials e.g. [[Kanban Framework]].<br /> <br /> ===Concrete Practice (25 Minutes)===<br /> # Ask the attendees to construct their respective Kanban diagrams with the materials provided.<br /> <br /> ===Conclusions (15 Minutes)===<br /> # Finish up with a team share back to discuss their posters to the attendees<br /> # Finally show a diagram of the [[Kanban Framework]] and walk the attendees through it paying attention to:<br /> #* the feedback loops<br /> #* the underlying philosophies [[Eliminating Waste]] and [[Smoothing the Flow of Work]]<br /> #* how the framework embodies the [[Agile Manifesto]]<br /> <br /> ==References==<br /> * Training From The Back of The Room, Sharon L. Bowman, Pfeiffer, 2009<br /> * https://weisbart.com/byos, Adam Weisbart, accessed 2018<br /> <br /> ==See Also==<br /> * [[Build Your Scrum Framework]]<br /> * [[Build Your Agile Flow]]</div>

Mmusij https://agileme.wiki/wiki/index.php?title=Build_Your_Agile_Flow&diff=1633 2023-06-30T00:25:01Z

<p>Mmusij: /* Conclusions (15 Minutes) */</p> <hr /> <div>[[Category:Agile:Workshops]][[Category:Agile]]<br /> ==Introduction==<br /> This exercise is related to [[Build Your Scrum Framework]] and allows leaders to build a diagram of a proposed Agile ecosystem for discussion. <br /> <br /> The workshop structure is based upon the 4 C’s framework described in Sharon Bowman’s Training From The Back of The Room (2009) (Bowman 2009).<br /> <br /> ==Learning Objectives==<br /> * Understand how an Agile ecosystem would exist in their organisation and gives rise to discussions about particular aspects<br /> <br /> ==Materials==<br /> * Printed [[Media:BYO_Agile_Flow.pdf|Agile Flow shapes]] 1 per group<br /> * Flip chart paper, 1 for each table group<br /> * Blu-tac or similar for sticking to the walls<br /> * Scissors<br /> <br /> &lt;pdf width=&quot;300&quot; height=&quot;500&quot;&gt;File:BYO_Agile_Flow.pdf&lt;/pdf&gt;<br /> <br /> ==Workshop Flow==<br /> ===Connections (5 Minutes)===<br /> # Start by asking the attendees to split into table groups of 4 and to acquire the necessary materials to start for each table group.<br /> <br /> ===Concepts (10 Minutes)===<br /> # Introduce the printed materials and have a brief discussion on the various items and what they stand for.<br /> <br /> ===Concrete Practice (25 Minutes)===<br /> # Ask the attendees to construct their respective Agile flow diagram on a sheet of flip chart paper.<br /> <br /> ===Conclusions (15 Minutes)===<br /> # Conclude with a show and tell with each table group presenting their posters to the attendees<br /> # Facilitate any questions with the models<br /> # Finish up with a team share back to discuss their models<br /> <br /> ==References==<br /> * Training From The Back of The Room, Sharon L. Bowman, Pfeiffer, 2009<br /> * https://weisbart.com/byos, Adam Weisbart, accessed 2018<br /> <br /> ==See Also==<br /> * [[Build Your Scrum Framework]]<br /> * [[Build Your Kanban Framework]]</div>

Mmusij https://agileme.wiki/wiki/index.php?title=Build_Your_Agile_Flow&diff=1632 2023-06-30T00:23:19Z

<p>Mmusij: /* Concrete Practice (25 Minutes) */</p> <hr /> <div>[[Category:Agile:Workshops]][[Category:Agile]]<br /> ==Introduction==<br /> This exercise is related to [[Build Your Scrum Framework]] and allows leaders to build a diagram of a proposed Agile ecosystem for discussion. <br /> <br /> The workshop structure is based upon the 4 C’s framework described in Sharon Bowman’s Training From The Back of The Room (2009) (Bowman 2009).<br /> <br /> ==Learning Objectives==<br /> * Understand how an Agile ecosystem would exist in their organisation and gives rise to discussions about particular aspects<br /> <br /> ==Materials==<br /> * Printed [[Media:BYO_Agile_Flow.pdf|Agile Flow shapes]] 1 per group<br /> * Flip chart paper, 1 for each table group<br /> * Blu-tac or similar for sticking to the walls<br /> * Scissors<br /> <br /> &lt;pdf width=&quot;300&quot; height=&quot;500&quot;&gt;File:BYO_Agile_Flow.pdf&lt;/pdf&gt;<br /> <br /> ==Workshop Flow==<br /> ===Connections (5 Minutes)===<br /> # Start by asking the attendees to split into table groups of 4 and to acquire the necessary materials to start for each table group.<br /> <br /> ===Concepts (10 Minutes)===<br /> # Introduce the printed materials and have a brief discussion on the various items and what they stand for.<br /> <br /> ===Concrete Practice (25 Minutes)===<br /> # Ask the attendees to construct their respective Agile flow diagram on a sheet of flip chart paper.<br /> <br /> ===Conclusions (15 Minutes)===<br /> # Conclude with a show and tell with each table group presenting their models to the attendees<br /> # Facilitate any questions with the models<br /> # Finish up with a team share back to discuss their models<br /> <br /> ==References==<br /> * Training From The Back of The Room, Sharon L. Bowman, Pfeiffer, 2009<br /> * https://weisbart.com/byos, Adam Weisbart, accessed 2018<br /> <br /> ==See Also==<br /> * [[Build Your Scrum Framework]]<br /> * [[Build Your Kanban Framework]]</div>

Mmusij https://agileme.wiki/wiki/index.php?title=Build_Your_Agile_Flow&diff=1631 2023-06-30T00:21:46Z

<p>Mmusij: /* Materials */</p> <hr /> <div>[[Category:Agile:Workshops]][[Category:Agile]]<br /> ==Introduction==<br /> This exercise is related to [[Build Your Scrum Framework]] and allows leaders to build a diagram of a proposed Agile ecosystem for discussion. <br /> <br /> The workshop structure is based upon the 4 C’s framework described in Sharon Bowman’s Training From The Back of The Room (2009) (Bowman 2009).<br /> <br /> ==Learning Objectives==<br /> * Understand how an Agile ecosystem would exist in their organisation and gives rise to discussions about particular aspects<br /> <br /> ==Materials==<br /> * Printed [[Media:BYO_Agile_Flow.pdf|Agile Flow shapes]] 1 per group<br /> * Flip chart paper, 1 for each table group<br /> * Blu-tac or similar for sticking to the walls<br /> * Scissors<br /> <br /> &lt;pdf width=&quot;300&quot; height=&quot;500&quot;&gt;File:BYO_Agile_Flow.pdf&lt;/pdf&gt;<br /> <br /> ==Workshop Flow==<br /> ===Connections (5 Minutes)===<br /> # Start by asking the attendees to split into table groups of 4 and to acquire the necessary materials to start for each table group.<br /> <br /> ===Concepts (10 Minutes)===<br /> # Introduce the printed materials and have a brief discussion on the various items and what they stand for.<br /> <br /> ===Concrete Practice (25 Minutes)===<br /> # Ask the attendees to construct their respective Agile flow using any means necessary e.g. using any web based resources they can find.<br /> <br /> ===Conclusions (15 Minutes)===<br /> # Conclude with a show and tell with each table group presenting their models to the attendees<br /> # Facilitate any questions with the models<br /> # Finish up with a team share back to discuss their models<br /> <br /> ==References==<br /> * Training From The Back of The Room, Sharon L. Bowman, Pfeiffer, 2009<br /> * https://weisbart.com/byos, Adam Weisbart, accessed 2018<br /> <br /> ==See Also==<br /> * [[Build Your Scrum Framework]]<br /> * [[Build Your Kanban Framework]]</div>

Mmusij https://agileme.wiki/wiki/index.php?title=Build_Your_Kanban_Framework&diff=1630 2023-06-29T07:38:57Z

<p>Mmusij: </p> <hr /> <div>[[Category:Agile:Workshops]][[Category:Agile]]<br /> ==Introduction==<br /> This exercise is related to [[Build Your Scrum Framework]] and allows attendees to have a go at building a diagram of the [[Kanban Framework]]. The workshop structure is based upon the 4 C’s framework described in Sharon Bowman’s Training From The Back of The Room (2009) (Bowman 2009).<br /> <br /> ==Learning Objectives==<br /> * Begin to understand how the Kanban framework fits with events, roles and artefacts<br /> <br /> ==Materials==<br /> * Copies of the [[Media:Kanban_Framework.jpg|Kanban poster]], 1 per group<br /> <br /> ===If Using Tactile &amp; Physical Media For Training===<br /> * Printed [[Media:Kanban_Framework_Shapes.pdf|framework shapes]] 1 per group<br /> * Printed [[Media:Scrum_Framework_Arrows.pdf|arrows]] 1 per group<br /> * Flip chart paper, 1 for each table group<br /> * Blu-tac or similar for sticking to the walls<br /> * Scissors<br /> <br /> ===If Using Electronic Distributed Training===<br /> * [[Media:Build_Your_Kanban_-_For_Distributed.pptx|PowerPoint Presentation]] by Stuart Bargon with the shapes as movable objects<br /> ** Instead of using the cut outs and flip chart paper, try hosting the presentation in design mode whilst sharing the screen with a video conference tool<br /> ** Now the teams can take control of the screen and move the shapes around to design their model<br /> <br /> &lt;pdf width=&quot;300&quot; height=&quot;500&quot;&gt;File:Kanban_Framework_Shapes.pdf&lt;/pdf&gt;<br /> <br /> ==Workshop Flow==<br /> ===Connections (5 Minutes)===<br /> # Start by asking the attendees to split into table groups of 4 and to acquire the necessary materials to start for each table group.<br /> <br /> ===Concepts (10 Minutes)===<br /> # Introduce the reading materials e.g. [[Kanban Framework]].<br /> <br /> ===Concrete Practice (25 Minutes)===<br /> # Ask the attendees to construct their respective Kanban models using any means necessary e.g. using any web based resources they can find.<br /> <br /> ===Conclusions (15 Minutes)===<br /> # Conclude with a show and tell with each table group presenting their models to the attendees<br /> # Facilitate any questions with the models<br /> # Finish up with a team share back to discuss their models<br /> # Finally show a diagram of the [[Kanban Framework]] and walk the attendees through it paying attention to:<br /> #* the feedback loops<br /> #* the underlying philosophies [[Eliminating Waste]] and [[Smoothing the Flow of Work]]<br /> #* how the framework embodies the [[Agile Manifesto]]<br /> <br /> ==References==<br /> * Training From The Back of The Room, Sharon L. Bowman, Pfeiffer, 2009<br /> * https://weisbart.com/byos, Adam Weisbart, accessed 2018<br /> <br /> ==See Also==<br /> * [[Build Your Scrum Framework]]<br /> * [[Build Your Agile Flow]]</div>

Mmusij https://agileme.wiki/wiki/index.php?title=Build_Your_Agile_Flow&diff=1629 2023-06-29T07:38:33Z

<p>Mmusij: </p> <hr /> <div>[[Category:Agile:Workshops]][[Category:Agile]]<br /> ==Introduction==<br /> This exercise is related to [[Build Your Scrum Framework]] and allows leaders to build a diagram of a proposed Agile ecosystem for discussion. <br /> <br /> The workshop structure is based upon the 4 C’s framework described in Sharon Bowman’s Training From The Back of The Room (2009) (Bowman 2009).<br /> <br /> ==Learning Objectives==<br /> * Understand how an Agile ecosystem would exist in their organisation and gives rise to discussions about particular aspects<br /> <br /> ==Materials==<br /> <br /> ===If Using Tactile &amp; Physical Media For Training===<br /> * Printed [[Media:BYO_Agile_Flow.pdf|Agile Flow shapes]] 1 per group<br /> * Flip chart paper, 1 for each table group<br /> * Blu-tac or similar for sticking to the walls<br /> * Scissors<br /> <br /> &lt;pdf width=&quot;300&quot; height=&quot;500&quot;&gt;File:BYO_Agile_Flow.pdf&lt;/pdf&gt;<br /> <br /> ==Workshop Flow==<br /> ===Connections (5 Minutes)===<br /> # Start by asking the attendees to split into table groups of 4 and to acquire the necessary materials to start for each table group.<br /> <br /> ===Concepts (10 Minutes)===<br /> # Introduce the printed materials and have a brief discussion on the various items and what they stand for.<br /> <br /> ===Concrete Practice (25 Minutes)===<br /> # Ask the attendees to construct their respective Agile flow using any means necessary e.g. using any web based resources they can find.<br /> <br /> ===Conclusions (15 Minutes)===<br /> # Conclude with a show and tell with each table group presenting their models to the attendees<br /> # Facilitate any questions with the models<br /> # Finish up with a team share back to discuss their models<br /> <br /> ==References==<br /> * Training From The Back of The Room, Sharon L. Bowman, Pfeiffer, 2009<br /> * https://weisbart.com/byos, Adam Weisbart, accessed 2018<br /> <br /> ==See Also==<br /> * [[Build Your Scrum Framework]]<br /> * [[Build Your Kanban Framework]]</div>

Mmusij https://agileme.wiki/wiki/index.php?title=Build_Your_Agile_Flow&diff=1628 2023-06-29T07:35:08Z

<p>Mmusij: Created page with &quot;Category:Agile:WorkshopsCategory:Agile ==Introduction== This exercise is related to Build Your Scrum Framework and allows leaders to build a diagram of a proposed Agile ecosystem for discussion. The workshop structure is based upon the 4 C’s framework described in Sharon Bowman’s Training From The Back of The Room (2009) (Bowman 2009). ==Learning Objectives== * Understand how an Agile ecosystem would exist in their organisation and gives rise to discussi...&quot;</p> <hr /> <div>[[Category:Agile:Workshops]][[Category:Agile]]<br /> ==Introduction==<br /> This exercise is related to [[Build Your Scrum Framework]] and allows leaders to build a diagram of a proposed Agile ecosystem for discussion. The workshop structure is based upon the 4 C’s framework described in Sharon Bowman’s Training From The Back of The Room (2009) (Bowman 2009).<br /> <br /> ==Learning Objectives==<br /> * Understand how an Agile ecosystem would exist in their organisation and gives rise to discussions about particular aspects<br /> <br /> ==Materials==<br /> <br /> ===If Using Tactile &amp; Physical Media For Training===<br /> * Printed [[Media:BYO_Agile_Flow.pdf|agile flow shapes]] 1 per group<br /> * Flip chart paper, 1 for each table group<br /> * Blu-tac or similar for sticking to the walls<br /> * Scissors<br /> <br /> &lt;pdf width=&quot;300&quot; height=&quot;500&quot;&gt;File:BYO_Agile_Flow.pdf&lt;/pdf&gt;<br /> <br /> ==Workshop Flow==<br /> ===Connections (5 Minutes)===<br /> # Start by asking the attendees to split into table groups of 4 and to acquire the necessary materials to start for each table group.<br /> <br /> ===Concepts (0 Minutes)===<br /> # Introduce the printed materials and have a brief discussion on the various items and what they stand for.<br /> <br /> ===Concrete Practice (25 Minutes)===<br /> # Ask the attendees to construct their respective Agile flow using any means necessary e.g. using any web based resources they can find.<br /> <br /> ===Conclusions (15 Minutes)===<br /> # Conclude with a show and tell with each table group presenting their models to the attendees<br /> # Facilitate any questions with the models<br /> # Finish up with a team share back to discuss their models<br /> <br /> ==References==<br /> * Training From The Back of The Room, Sharon L. Bowman, Pfeiffer, 2009<br /> * https://weisbart.com/byos, Adam Weisbart, accessed 2018<br /> <br /> ==See Also==<br /> * [[Build Your Scrum Framework]]<br /> * [[Build Your Kanban Framework]]</div>

Mmusij https://agileme.wiki/wiki/index.php?title=Build_Your_Scrum_Framework&diff=1627 2023-06-29T07:30:42Z

<p>Mmusij: </p> <hr /> <div>[[Category:Agile:Workshops]][[Category:Agile]]<br /> ==Introduction==<br /> This exercise is based upon Build Your Own Scrum, (Weisbart 2018), which was seen to be out of date with the latest Scrum Guide. The workshop structure is based upon the 4 C’s framework described in Sharon Bowman’s Training From The Back of The Room (2009) (Bowman 2009).<br /> <br /> ==Learning Objectives==<br /> * Begin to understand how the Scrum framework fits with events, roles and artefacts<br /> <br /> ==Materials==<br /> The materials needed for the workshop include:<br /> <br /> * Printed [[Media:Scrum_Framework_Shapes.pdf|framework shapes]] 1 per group<br /> * Printed [[Media:Scrum_Framework_Arrows.pdf|arrows]] 1 per group<br /> * Flip chart paper, 1 for each table group<br /> * Blu-tac or similar for sticking to the walls<br /> * Scissors<br /> * Copies of the [http://scrumguides.org Scrum Guide] document, 1 per group<br /> * Copies of the [http://scrumprimer.org Scrum Primer] document, 1 per group<br /> * Copies of the [[Media:Scrum.jpg|Scrum poster]], 1 per group<br /> <br /> &lt;pdf width=&quot;300&quot; height=&quot;500&quot;&gt;File:Scrum_Framework_Shapes.pdf&lt;/pdf&gt;<br /> <br /> ==Workshop Flow==<br /> ===Connections (5 Minutes)===<br /> # Start by asking the attendees to split into table groups of 4 and to acquire the necessary materials to start for each table group.<br /> <br /> ===Concepts (0 Minutes)===<br /> # Introduce the reading materials from the Scrum Guide or Scrum Primer.<br /> <br /> ===Concrete Practice (25 Minutes)===<br /> # Ask the attendees to construct their respective Scrum models using any means necessary e.g. using the handouts and any web based resources they can find.<br /> <br /> ===Conclusions (15 Minutes)===<br /> # Conclude with a show and tell with each table group presenting their models to the attendees<br /> # Facilitate any questions with the models<br /> # Finish up with a team share back to discuss their models<br /> # Finally show a diagram of the [[Scrum Framework]] and walk the attendees through it paying attention to:<br /> #* the feedback loops<br /> #* the nature of the [[Scrum Roles]]<br /> #* how the framework embodies the [[Agile Manifesto]]<br /> <br /> ==References==<br /> * Training From The Back of The Room, Sharon L. Bowman, Pfeiffer, 2009<br /> * https://weisbart.com/byos, Adam Weisbart, accessed 2018<br /> <br /> ==See Also==<br /> * [[Build Your Kanban Framework]]<br /> * [[Build Your Agile Flow]]</div>

Mmusij https://agileme.wiki/wiki/index.php?title=Build_Your_Kanban_Framework&diff=1626 2023-06-29T07:28:42Z

<p>Mmusij: </p> <hr /> <div>[[Category:Agile:Workshops]][[Category:Agile]]<br /> ==Introduction==<br /> This exercise is related to [[Build Your Scrum Framework]] and allows attendees to have a go at building a diagram of the [[Kanban Framework]]. The workshop structure is based upon the 4 C’s framework described in Sharon Bowman’s Training From The Back of The Room (2009) (Bowman 2009).<br /> <br /> ==Learning Objectives==<br /> * Begin to understand how the Kanban framework fits with events, roles and artefacts<br /> <br /> ==Materials==<br /> * Copies of the [[Media:Kanban_Framework.jpg|Kanban poster]], 1 per group<br /> <br /> ===If Using Tactile &amp; Physical Media For Training===<br /> * Printed [[Media:Kanban_Framework_Shapes.pdf|framework shapes]] 1 per group<br /> * Printed [[Media:Scrum_Framework_Arrows.pdf|arrows]] 1 per group<br /> * Flip chart paper, 1 for each table group<br /> * Blu-tac or similar for sticking to the walls<br /> * Scissors<br /> <br /> ===If Using Electronic Distributed Training===<br /> * [[Media:Build_Your_Kanban_-_For_Distributed.pptx|PowerPoint Presentation]] by Stuart Bargon with the shapes as movable objects<br /> ** Instead of using the cut outs and flip chart paper, try hosting the presentation in design mode whilst sharing the screen with a video conference tool<br /> ** Now the teams can take control of the screen and move the shapes around to design their model<br /> <br /> &lt;pdf width=&quot;300&quot; height=&quot;500&quot;&gt;File:Kanban_Framework_Shapes.pdf&lt;/pdf&gt;<br /> <br /> ==Workshop Flow==<br /> ===Connections (5 Minutes)===<br /> # Start by asking the attendees to split into table groups of 4 and to acquire the necessary materials to start for each table group.<br /> <br /> ===Concepts (0 Minutes)===<br /> # Introduce the reading materials e.g. [[Kanban Framework]].<br /> <br /> ===Concrete Practice (25 Minutes)===<br /> # Ask the attendees to construct their respective Kanban models using any means necessary e.g. using any web based resources they can find.<br /> <br /> ===Conclusions (15 Minutes)===<br /> # Conclude with a show and tell with each table group presenting their models to the attendees<br /> # Facilitate any questions with the models<br /> # Finish up with a team share back to discuss their models<br /> # Finally show a diagram of the [[Kanban Framework]] and walk the attendees through it paying attention to:<br /> #* the feedback loops<br /> #* the underlying philosophies [[Eliminating Waste]] and [[Smoothing the Flow of Work]]<br /> #* how the framework embodies the [[Agile Manifesto]]<br /> <br /> ==References==<br /> * Training From The Back of The Room, Sharon L. Bowman, Pfeiffer, 2009<br /> * https://weisbart.com/byos, Adam Weisbart, accessed 2018<br /> <br /> ==See Also==<br /> * [[Build Your Scrum Framework]]<br /> * [[Build Your Agile Flow]]</div>

Mmusij https://agileme.wiki/wiki/index.php?title=File:BYO_Agile_Flow.pdf&diff=1625 2023-06-29T07:23:21Z

<p>Mmusij: </p> <hr /> <div></div>

Mmusij https://agileme.wiki/wiki/index.php?title=Kanban_Simulation_With_Dice&diff=1624 2023-06-28T08:02:05Z

<p>Mmusij: </p> <hr /> <div>[[Category:Agile:Workshops]][[Category:Agile]]<br /> <br /> ==Learning Outcomes==<br /> This exercise provides some experience using a dice based simulation of [[Kanban Framework|Kanban]] to experience how a [[Visualising The Flow|Value Stream]] flow of work and [[Visualising The Flow#WIP Limits|Work In Progress (WIP) Limits]] work together, and to discover the strategies that you and your team can use to cope with responding to change.<br /> <br /> ==Prerequisites==<br /> A prerequisite for this exercise is that a [[Scrum Artefacts|Product Backlog]] exists with items that have been estimated with points using the [[Affinity Estimation]] technique such as at the end point of the [[My Sweet 16 Birthday Party]] exercise.<br /> <br /> ==Timings==<br /> Allow 40 mins for this exercise.<br /> <br /> ==Materials==<br /> * Dice, enough for tables groups to be able to throw up to 5 dice as a team<br /> * Marker pens<br /> * Post-it Notes<br /> <br /> ==Connections==<br /> # As a team sum up how many total points are on the Backlog of work and divide this number by 150 to indicate how many dice are needed<br /> # Ask the facilitator for the required number of dice to be issued to the team<br /> # Write on large post it notes headers called ''&quot;Next (6)&quot;'', ''&quot;Researching (3)&quot;'', ''&quot;Creating (2)&quot;'', ''&quot;Reviewing (3)&quot;'' and ''&quot;Done&quot;''<br /> # Arrange the headers in a value stream flow in order. Note that the numbers in the ''&quot;()&quot;'' are the Work in Progress Limits and indicate how many tickets can be in a column at any one time.<br /> # Pull in the first 6 items to work on from the Backlog and place them under the ''&quot;Next (6)&quot;'' header<br /> <br /> ==Concrete Practice==<br /> ===Rules===<br /> * The ''&quot;Next (6)&quot;'' column can be refilled at any time but can only have a maximum of 6 items in it<br /> * To progress an item the points estimate on the item indicates the effort needed to move it to the next column. This amount is spent and deducted from the current day's effort. Items are progressed through the columns with the corresponding effort spent from the current day's effort each time until there is no more current day's effort left.<br /> * Items that are too large to be progressed can be broken down into smaller items with new post it notes and placed in the ''&quot;Next (6)&quot;'' column<br /> <br /> [[File:Kanban simulation.jpg|500px|Kanban Simulation]]<br /> <br /> ===Steps===<br /> # Throw the dice for the current day's effort<br /> # Select the an item to be worked on from the ''&quot;Next (6)&quot;'' column and move it to the next column to the right deducting the points estimate from the current day's effort<br /> # Repeat the previous step until the current day's effort reaches zero<br /> # Throw the dice again for the next day and repeat the process until the maximum days for the work has been reached<br /> # Call over the facilitator for review and discussion.<br /> <br /> ==Closure==<br /> # Reflect on the exercise with some suggested questions:<br /> ## What decisions did you have to make?<br /> ## How did this affect your understanding of what you could do within the time available?<br /> ## What does this tell you about having a sense of flexibility and options in the Backlog?<br /> <br /> ==See Also==<br /> * [[Scrum Simulation With Dice]]<br /> * [[My Sweet 16 Birthday Party]]</div>

Mmusij https://agileme.wiki/wiki/index.php?title=File:Kanban_simulation.jpg&diff=1623 2023-06-28T07:59:20Z

<p>Mmusij: </p> <hr /> <div></div>

Mmusij https://agileme.wiki/wiki/index.php?title=Affinity_Estimation&diff=1622 2023-06-28T07:54:06Z

<p>Mmusij: /* Steps */</p> <hr /> <div>[[Category:Agile:Articles]][[Category:Agile]]<br /> <br /> Affinity Estimation is a very quick technique to help size backlog items with a rough ''rule of thumb'' approach, which is ideal when you have a lot of items to size or are creating a backlog of work for the first time.<br /> <br /> ==Steps==<br /> # Arrange the T-Shirt sizing categories along the top in a row, (can be done on a wall, floor or on a virtual board.)<br /> # Choose items from the backlog and arrange them under the corresponding T-Shirt size for the effort needed to complete them<br /> # Choose items from the S T-Shirt size and arrange them under a corresponding numerical sizes of 1, 2 or 3. (It can be easier to think of these as either a &quot;Small Small&quot; = 1 or a &quot;Medium Small&quot; = 2 or a &quot;Large Small&quot; = 3)<br /> # Repeat for the other T-Shirt sizes and arrange the items under the corresponding numerical size<br /> <br /> [[File:Affinity Estimation.jpeg|500px|Affinity Estimation]]<br /> <br /> ==80:20 Rule==<br /> This technique is great for quick sizing of a number of cards, and it is useful to consider that the estimation is good enough with an 80:20 rule, that is, 80% accuracy with 20% of the effort to do the sizing.<br /> <br /> ==Working With Large Groups==<br /> When working with large groups you might like to make the following modifications to the steps:<br /> * Allow everyone in the group to take a number of cards from the stack<br /> * Each member of the group sizes their collection of cards individually first<br /> * When all of the cards have been allocated to a sizing category, then work as small groups e.g. pairs or triads to look over the cards and adjust as necessary.<br /> <br /> ==See Also==<br /> * [[Agile Estimation]]<br /> * [[T-Shirt Sizing]]<br /> * [[Story Mapping]]<br /> <br /> ==References==<br /> #</div>

Mmusij https://agileme.wiki/wiki/index.php?title=Affinity_Estimation&diff=1621 2023-06-28T07:48:31Z

<p>Mmusij: /* Steps */</p> <hr /> <div>[[Category:Agile:Articles]][[Category:Agile]]<br /> <br /> Affinity Estimation is a very quick technique to help size backlog items with a rough ''rule of thumb'' approach, which is ideal when you have a lot of items to size or are creating a backlog of work for the first time.<br /> <br /> ==Steps==<br /> # Arrange the T-Shirt sizing categories along the top in a row, (can be done on a wall, floor or on a virtual board.)<br /> # Choose items from the backlog and arrange them under the corresponding T-Shirt size for the effort needed to complete them<br /> # Choose items from the S T-Shirt size and arrange them under a corresponding numerical sizes of 1, 2 or 3. (It can be easier to think of these as either a &quot;Small Small&quot; = 1 or a &quot;Medium Small&quot; = 2 or a &quot;Large Small&quot; = 3)<br /> # Repeat for the other T-Shirt sizes and arrange the items under the corresponding numerical size<br /> <br /> [[File:Affinity_Estimation.jpeg|500px|Affinity Estimation]]<br /> <br /> ==80:20 Rule==<br /> This technique is great for quick sizing of a number of cards, and it is useful to consider that the estimation is good enough with an 80:20 rule, that is, 80% accuracy with 20% of the effort to do the sizing.<br /> <br /> ==Working With Large Groups==<br /> When working with large groups you might like to make the following modifications to the steps:<br /> * Allow everyone in the group to take a number of cards from the stack<br /> * Each member of the group sizes their collection of cards individually first<br /> * When all of the cards have been allocated to a sizing category, then work as small groups e.g. pairs or triads to look over the cards and adjust as necessary.<br /> <br /> ==See Also==<br /> * [[Agile Estimation]]<br /> * [[T-Shirt Sizing]]<br /> * [[Story Mapping]]<br /> <br /> ==References==<br /> #</div>

Mmusij https://agileme.wiki/wiki/index.php?title=File:Affinity_Estimation.jpeg&diff=1620 2023-06-28T07:42:58Z

<p>Mmusij: Mmusij uploaded a new version of File:Affinity Estimation.jpeg</p> <hr /> <div></div>

Mmusij https://agileme.wiki/wiki/index.php?title=Agile_102_Workshop_Syllabus&diff=1619 2023-06-28T07:10:20Z

<p>Mmusij: /* Concepts and Concrete Practice */</p> <hr /> <div>[[Category:Agile:Articles]][[Category:Agile:Scrum]][[Category:Agile:Kanban]][[Category:Agile]][[Category:Agile:Workshops]]<br /> <br /> After the practical exercise in the [[Agile 101 Workshop Syllabus|Agile 101 Workshop]], this workshop focuses on developing teams' ability to apply some of their experiences to another simulation project, which needs a next level understanding of the Agile concepts.<br /> <br /> This workshop sees teams building a [[Scrum Artefacts|Product Backlog]] as a [[Story Mapping|Story Map]] and devising a release plan. Finally, the attendees run their release plan through a dice based simulation of [[Scrum Framework|Scrum]] and make release and scoping decisions to try to get the best possible outcome in the simulation.<br /> <br /> ==Materials==<br /> * Large poster illustrating the Agile framework for the session such as [[Scrum Framework|Scrum]] for example<br /> * Flip chart paper and markers<br /> * Post-it notes and markers<br /> * A4 spare paper<br /> * Dice, enough for pairs of attendees to be able to throw up to 3 dice<br /> * Visible timer to indicate the time left for the activities<br /> * Music playlist and sound system to help play low level music whilst the teams are working<br /> * [[Debrief Cards]]<br /> * Any materials for the exercises during the Concrete Practice section<br /> <br /> ==Setup==<br /> The setup for the room with up to 16 participants includes:<br /> <br /> * Large poster of the Agile framework to be used visible on the wall<br /> * Several workstations arranged in cafe seating available for multiple table groups<br /> <br /> [[File:Agile_101_Workshop.jpeg|600px|Agile 101 Part 2 Workshop Setup]]<br /> <br /> ==Connections==<br /> Provide 3 hours for teams to orientate themselves to their project, conduct 4 iterations or [[Sprints]] and conclude with a reflection:<br /> # Introduction and orientation of the approach:<br /> ## Team self selection<br /> ## Team name poster and workstation setup<br /> <br /> ==Concepts and Concrete Practice==<br /> # Start with building a Product Backlog and release plan together e.g. following the [[My Sweet 16 Birthday Party]] exercise<br /> # Run through an agile simulation to put the release plan into play e.g. following the [[Kanban Simulation With Dice]] or [[Scrum Simulation With Dice]] exercise<br /> <br /> ==Closure==<br /> # Host an overall share back and reflection on the workshop with [[Debrief Cards]] if needed<br /> <br /> ==See Also==<br /> * [[Agile 101 Workshop Syllabus]]<br /> * [[My Sweet 16 Birthday Party]]<br /> * [[Kanban Simulation With Dice]]<br /> * [[Scrum Simulation With Dice]]<br /> <br /> ==References==<br /> * [https://www.scrumalliance.org/ScrumRedesignDEVSite/media/ScrumAllianceMedia/Files%20and%20PDFs/Certifications/Foundational/Foundational_LearningObjectives.pdf Scrum Foundations Learning Objectives], accessed 21 Jan 2019</div>

Mmusij https://agileme.wiki/wiki/index.php?title=Agile_102_Workshop_Syllabus&diff=1618 2023-06-28T07:10:01Z

<p>Mmusij: /* See Also */</p> <hr /> <div>[[Category:Agile:Articles]][[Category:Agile:Scrum]][[Category:Agile:Kanban]][[Category:Agile]][[Category:Agile:Workshops]]<br /> <br /> After the practical exercise in the [[Agile 101 Workshop Syllabus|Agile 101 Workshop]], this workshop focuses on developing teams' ability to apply some of their experiences to another simulation project, which needs a next level understanding of the Agile concepts.<br /> <br /> This workshop sees teams building a [[Scrum Artefacts|Product Backlog]] as a [[Story Mapping|Story Map]] and devising a release plan. Finally, the attendees run their release plan through a dice based simulation of [[Scrum Framework|Scrum]] and make release and scoping decisions to try to get the best possible outcome in the simulation.<br /> <br /> ==Materials==<br /> * Large poster illustrating the Agile framework for the session such as [[Scrum Framework|Scrum]] for example<br /> * Flip chart paper and markers<br /> * Post-it notes and markers<br /> * A4 spare paper<br /> * Dice, enough for pairs of attendees to be able to throw up to 3 dice<br /> * Visible timer to indicate the time left for the activities<br /> * Music playlist and sound system to help play low level music whilst the teams are working<br /> * [[Debrief Cards]]<br /> * Any materials for the exercises during the Concrete Practice section<br /> <br /> ==Setup==<br /> The setup for the room with up to 16 participants includes:<br /> <br /> * Large poster of the Agile framework to be used visible on the wall<br /> * Several workstations arranged in cafe seating available for multiple table groups<br /> <br /> [[File:Agile_101_Workshop.jpeg|600px|Agile 101 Part 2 Workshop Setup]]<br /> <br /> ==Connections==<br /> Provide 3 hours for teams to orientate themselves to their project, conduct 4 iterations or [[Sprints]] and conclude with a reflection:<br /> # Introduction and orientation of the approach:<br /> ## Team self selection<br /> ## Team name poster and workstation setup<br /> <br /> ==Concepts and Concrete Practice==<br /> # Start with building a Product Backlog and release plan together e.g. following the [[My Sweet 16 Birthday Party]] exercise<br /> # Run through an agile simulation to put the release plan into play e.g. following the [[Scrum Simulation With Dice]] exercise<br /> <br /> ==Closure==<br /> # Host an overall share back and reflection on the workshop with [[Debrief Cards]] if needed<br /> <br /> ==See Also==<br /> * [[Agile 101 Workshop Syllabus]]<br /> * [[My Sweet 16 Birthday Party]]<br /> * [[Kanban Simulation With Dice]]<br /> * [[Scrum Simulation With Dice]]<br /> <br /> ==References==<br /> * [https://www.scrumalliance.org/ScrumRedesignDEVSite/media/ScrumAllianceMedia/Files%20and%20PDFs/Certifications/Foundational/Foundational_LearningObjectives.pdf Scrum Foundations Learning Objectives], accessed 21 Jan 2019</div>

Mmusij https://agileme.wiki/wiki/index.php?title=Kanban_Simulation_With_Dice&diff=1617 2023-06-28T07:09:05Z

<p>Mmusij: Created page with &quot;Category:Agile:WorkshopsCategory:Agile ==Learning Outcomes== This exercise provides some experience using a dice based simulation of Kanban to experience how a Value Stream flow of work and Work In Progress (WIP) Limits work together, and to discover the strategies that you and your team can use to cope with responding to change. ==Prerequisites== A prerequisite for this exercise...&quot;</p> <hr /> <div>[[Category:Agile:Workshops]][[Category:Agile]]<br /> <br /> ==Learning Outcomes==<br /> This exercise provides some experience using a dice based simulation of [[Kanban Framework|Kanban]] to experience how a [[Visualising The Flow|Value Stream]] flow of work and [[Visualising The Flow#WIP Limits|Work In Progress (WIP) Limits]] work together, and to discover the strategies that you and your team can use to cope with responding to change.<br /> <br /> ==Prerequisites==<br /> A prerequisite for this exercise is that a [[Scrum Artefacts|Product Backlog]] exists with items that have been estimated with points using the [[Affinity Estimation]] technique such as at the end point of the [[My Sweet 16 Birthday Party]] exercise.<br /> <br /> ==Timings==<br /> Allow 40 mins for this exercise.<br /> <br /> ==Materials==<br /> * Dice, enough for tables groups to be able to throw up to 5 dice as a team<br /> * Marker pens<br /> * Post-it Notes<br /> <br /> ==Connections==<br /> # As a team sum up how many total points are on the Backlog of work and divide this number by 150 to indicate how many dice are needed<br /> # Ask the facilitator for the required number of dice to be issued to the team<br /> # Write on large post it notes headers called ''&quot;Next (6)&quot;'', ''&quot;Researching (3)&quot;'', ''&quot;Creating (2)&quot;'', ''&quot;Reviewing (3)&quot;'' and ''&quot;Done&quot;''<br /> # Arrange the headers in a value stream flow in order. Note that the numbers in the ''&quot;()&quot;'' are the Work in Progress Limits and indicate how many tickets can be in a column at any one time.<br /> # Pull in the first 6 items to work on from the Backlog and place them under the ''&quot;Next (6)&quot;'' header<br /> <br /> ==Concrete Practice==<br /> ===Rules===<br /> * The ''&quot;Next (6)&quot;'' column can be refilled at any time but can only have a maximum of 6 items in it<br /> * To progress an item the points estimate on the item indicates the effort needed to move it to the next column. This amount is spent and deducted from the current day's effort. Items are progressed through the columns with the corresponding effort spent from the current day's effort each time until there is no more current day's effort left.<br /> * Items that are too large to be progressed can be broken down into smaller items with new post it notes and placed in the ''&quot;Next (6)&quot;'' column<br /> <br /> ===Steps===<br /> # Throw the dice for the current day's effort<br /> # Select the an item to be worked on from the ''&quot;Next (6)&quot;'' column and move it to the next column to the right deducting the points estimate from the current day's effort<br /> # Repeat the previous step until the current day's effort reaches zero<br /> # Throw the dice again for the next day and repeat the process until the maximum days for the work has been reached<br /> # Call over the facilitator for review and discussion.<br /> <br /> ==Closure==<br /> # Reflect on the exercise with some suggested questions:<br /> ## What decisions did you have to make?<br /> ## How did this affect your understanding of what you could do within the time available?<br /> ## What does this tell you about having a sense of flexibility and options in the Backlog?<br /> <br /> ==See Also==<br /> * [[Scrum Simulation With Dice]]<br /> * [[My Sweet 16 Birthday Party]]</div>

Mmusij https://agileme.wiki/wiki/index.php?title=File:Coaching_Canvas.pdf&diff=1616 2023-04-17T21:17:20Z

<p>Mmusij: Mmusij uploaded a new version of File:Coaching Canvas.pdf</p> <hr /> <div></div>

Mmusij https://agileme.wiki/wiki/index.php?title=File:Coaching_Canvas.pdf&diff=1615 2023-04-17T07:34:45Z

<p>Mmusij: Mmusij uploaded a new version of File:Coaching Canvas.pdf</p> <hr /> <div></div>

Mmusij https://agileme.wiki/wiki/index.php?title=Release_Strategy&diff=1614 2022-10-27T01:04:29Z

<p>Mmusij: /* Delivery Focus */</p> <hr /> <div>[[Category:Agile:Articles]][[Category:Agile]]<br /> <br /> ==Delivery Focus==<br /> Teams that only consider a superficial understanding of the work tend to adopt a reactionary ''conveyor belt'' style of working that orders the Product Backlog and then progressively works through each of the items in order without too much thought about why it is needed or any sense of adaptation. They drop into a ''delivery focus'' where the deadline and the number of items delivered becomes more important than what ''value'' is being delivered to the customer. The metrics and efficient delivery becomes more important than the value delivered. <br /> <br /> There also seems to be an underlying assumption that all items are of equal value, and that more incremental delivery of items equals more value delivered. Which is not necessarily the case. More value delivered is more value delivered.<br /> <br /> ==Value Focus==<br /> Teams that have more customer awareness tend to focus on the value of items and how to deliver that value. They will explore, prototype and seek feedback to see what resonates with customers throughout the delivery of the work, and actively adapt what they are doing accordingly. Here there is also a tendency to accept that not all items on the backlog are equal and that some items are more valuable than others, which presents opportunities and options to exploit. More emphasis and effort may be placed on higher value items, and lower emphasis and effort on lower value items.<br /> <br /> Additionally, teams with high value focus will not look to deliver the whole backlog of items, but will instead look to maximise the value from the backlog. When the backlog ceases to yield sufficient value in the eyes of the customer, then they will look to move on to another body of work. Hence, not all of the items on the backlog may be worked on, which can be quite sobering for delivery focused teams.<br /> <br /> ''Value'' is also subjective and socially created, which also means that perceived value can change over time. This then prompts teams to continually test their assumptions with customers throughout the work to understand where they are adding value, and where the highest yield of value is on the backlog, which they accept is not a static quality and may change and migrate.<br /> <br /> ==Risk Focus==<br /> Some bodies of work present key risks, such as, integration risk for a central framework that needs to connect to several services for example, or a new app that has a volatile value proposition in the eyes of the customer. Teams with a good awareness of the key risks in the body of their work will tend to address those risks head on in the early iterations. Neutralising the risks early then takes the anxiety out of the work and the team can then focus on how to make the product better with each successive iteration. <br /> <br /> For the example with the central framework, the integration risk may be neutralised straight away using a ''steel thread'' [[Backlog Strategy Archetypes|Backlog Strategy Archetype]] that looks to connect each of the services together from the outset of the work using a simple ''ping'' for example. Here the integration risk has been neutralised straight away and now the team can focus on adding value on top of this rudimentary connection in successive iterations.<br /> <br /> The value proposition example may involve initially prototyping multiple approaches for the apps and getting out their and interacting with potential customers to see what resonates and what doesn't. The initial investment to prototype then furnishes the team with more knowledge about what will resonate and what does not, helping them to refine their backlog and adapt their approaches accordingly.<br /> <br /> ==Exploration Focus==<br /> Teams that are not sure of what the problem is let alone what the solution is, may respond to this situation with successive prototypes to learn about problem space and the solution space. Working closely with customers and stakeholders to continually refine their prototypes and narrow down where the value proposition is with regards the problem to solve, and the solution to solve it.<br /> <br /> A backlog of work may well invest initially in prototyping with a view to converging and narrowing the scope to what the problem really is and a valuable solution for it in later iterations.<br /> <br /> ==Multi Release Strategies==<br /> When working with multiple releases it is always good to consider whether you are ''releasing to earn'' or ''releasing to learn''. The latter implying a rapid release cycle to actively foster and then respond to feedback.<br /> <br /> Organisations that are used to infrequent and large releases tend to defend their approach by citing risk concerns and that releasing less often reduces the risk. As a result, the releases tend to be large, cumbersome and often too complex to provide any degree of risk mitigation.<br /> <br /> Conversely, releasing more often with smaller releases provides a risk mitigation strategy of managing small amounts of risk more often. The releases are small, easily managed, less complex and we get more practice at releasing, which improves the probability of releasing even faster, especially if this can be automated.<br /> <br /> ===Minimum Viable Product (MVP)===<br /> Organisations that are in their infancy with Agile approaches and have traditionally worked with projects and large infrequent releases often misuse this approach and consider the MVP to be the basic release, or in the worst case, a substitute for the word “release”. Conversations often take place about what is in or out of the MVP, which when translated often means which items are in or out of the release.<br /> <br /> [[File:Multi Release Strategies.jpg|500px|Multi Release Strategies]]<br /> <br /> MVP was always intended as a multi release strategy, with the intention being to provide something into the market quickly that isn’t necessarily going to earn any revenue or even customer loyalty, but the information and feedback gained can be invaluable for the next release in an evolutionary strategy. If some revenue can be earned whilst the project is still running then that can be used to offset the cost of development, which relieves the commercial pressure.<br /> <br /> ===Minimum Marketable Product (MMP)===<br /> This is also a multi release strategy with the prime focus being on the ability to learn from customers and end users, testing assumptions and the market with an idea. The feedback translates into hypotheses for future releases and navigates the product towards the customer desires.<br /> <br /> ==See Also==<br /> * [[Product Owner]]<br /> * [[Purpose &amp; Strategy]]<br /> * [[Evolutionary Strategy]]<br /> * [[Strategic Awareness]]<br /> * [[Backlog Strategy]]<br /> * [[Backlog Strategy Archetypes]]</div>

Mmusij