Agile transformation strategy

914
-1

Published on

Published in: Design, Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
914
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • What and HowTest and Dev pitted against each otherManager Fair play
  • http://agilemanagement.net/index.php/Blog/the_principles_of_the_kanban_method
  • Agile transformation strategy

    1. 1. Agile Transformation Strategy<br />Ajit Alwe<br />
    2. 2. Agile Transformation Strategy – Big Picture <br />Kanban – David Anderson School<br />3 foundational principles:<br />Start with what you do now<br />Agree to pursue incremental, evolutionary change<br />Respect the current process, roles, responsibilities & titles <br /><ul><li>XP = Scrum + Software Engineering
    3. 3. Model for Customizing XP</li></ul>Evolutionary TransformationStrategy to move towards agile<br />Agile S/W engineering process<br />Existing S/W engineering process<br />Mgmt framework that gels with Agile way of s/w dev<br />Existing mgmt framework<br />?<br />Mgmt framework includes<br /><ul><li> Org/Communication Structure
    4. 4. Accountability Hierarchy
    5. 5. Performance measurements
    6. 6. Incentives</li></ul>unknown<br />
    7. 7. Model for Customizing Agile(XP) Software Process by- Glenn Vanderburg<br />Src - <br />http://vanderburg.org/Writing/xpannealed.pdf<br />
    8. 8. Model for Customizing Agile(XP) Software Process<br />Co-relation of XP-practices to feedback they provide about particular kinds of decisions, from very small to the large, sweeping decisions<br />
    9. 9. Model for Customizing Agile(XP) Software Process<br />Correspondence between XP-practices and time scales<br />
    10. 10. Kanban – David Anderson School<br />3 Foundational principles<br />Start with what you do now<br />Agree to pursue incremental, evolutionary change<br />Respect the current process, roles, responsibilities & titles<br />5 Core properties<br />Visualize the workflow<br /> Limit WIP<br /> Manage Flow<br /> Make Process Policies Explicit<br /> Improve Collaboratively (using models & the scientific method)<br />Src http://agilemanagement.net/index.php/Blog/the_principles_of_the_kanban_method<br />
    11. 11. First Step<br />Visualize the workflow<br />
    12. 12. Cumulative Flow Diagram<br /><ul><li>Multi-dimensional giving overall picture, gives info on WIP, bottle-necks, rate of development
    13. 13. Gives both the information given by Sprint Burn down and Release Burn Down (i.e velocity)
    14. 14. Cost of collecting data is low
    15. 15. Gives information to all the stakeholder, potentially cutting down the meeting times</li></li></ul><li>Minimum Requirement to Visualize the flow<br />Create backlog items, containing either Feature list or Functional Test Cases.<br />Make sure the items are equal sized or grouped into small, medium, large size<br />Excel Template to generate Cumulative Flow diagram. (working with Jay/Akas to figure out ques in their respective projects)<br />
    16. 16. Game to sensitize people on Kanban concepts<br />http://www.getkanban.com/BoardGame<br />

    ×