1 / 31

Introducing Agile and Lean Practices into a Chaotic Environment

Introducing Agile and Lean Practices into a Chaotic Environment. An overview of what practices the team was using 6 months ago. Where We Were THEN. Team. Brand new 4 Developers No Tester No Project Manager Product Owner shared. Cadence / Capacity Management. “Shock Therapy” Scrum

zoltin
Download Presentation

Introducing Agile and Lean Practices into a Chaotic Environment

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Introducing Agile and Lean Practices into a Chaotic Environment

  2. An overview of what practices the team was using 6 months ago Where We Were THEN

  3. Team • Brand new • 4 Developers • No Tester • No Project Manager • Product Owner shared

  4. Cadence / Capacity Management • “Shock Therapy” Scrum • 1 week iterations • Short feedback cycles

  5. Meetings • Prioritisation • Occurs iteration – 1 • Requirements / Analysis • Planning • Stand Up • Demo • Retrospective

  6. Analysis • Whole team and Stakeholder for feature • Whiteboard • Converted to scenarios (G,W,T) after meeting

  7. Task Board

  8. Estimation • Occurs at planning meeting • Planning Poker • Story Points using Fibonacci Sequence • Unable to do longer term planning at this stage as not enough data but points were very helpful

  9. Testing / QA • All testing done by the developers • Nobody tested their own work though!

  10. Continuous Integration • All Projects were under CI • Some deployments done using CI • Working towards having all deployments automated

  11. Development Practices • Pair Programming, Unit Testing, Refactoring and more • Coding Standards – Document and Resharper • All new code; Unit Tests, Integration Tests, Acceptance Tests

  12. Team Principles • No multi-tasking • All new or changed code must be thoroughly unit tested • No more than 2 pieces of work in “Active Work” at any time (our team is 3 developers) • We always work on the highest priority task • Our definition of done is “In UAT” • Leave it in a better condition than you found it • No hidden work • No overtime • No disruptions • Don’t SysTest your own work (we don’t have a tester yet)

  13. Which practices are we using now? Where we are now

  14. Team • 5 Developers • Dedicated Tester • No Project Manager • Product Owner shared

  15. Cadence / Capacity Management • 1 week iterations • Short feedback cycles • Less Meetings overhead • Meetings when needed

  16. Meetings • Prioritisation • Occurs iteration – 1 • Requirements / Analysis • Planning • Stand Up • Demo – When we can… • Fortnightly Retrospectives

  17. Analysis • Merged with Prioritisation Session • Whole Team and Stakeholders • Whiteboard • Convert to scenarios (G,W,T) after meeting • Team proposes features too

  18. Task Board

  19. Estimation • Occurs at Analysis meeting • T – Shirt Sizes • Estimation • Occurs at planning meeting • T-Shirt sized estimates • Can do longer term planning • Delivery road map

  20. Testing / QA • All testing lead by the tester • Some testing done by developers • Automated acceptance tests

  21. Continuous Integration • All projects now under CI • CI runs acceptance tests after deployment • Fully automated deployment to Live

  22. Development Practices • Pair Programming, Unit Testing, Refactoring and more • Coding Standards – Document and Resharper • All new code = Unit Tests, Integration Tests, Acceptance Tests • More effort spent on Acceptance Tests

  23. Code Metrics • CI generates a code metrics dashboard, using NDepend on every check-in • Visibility into code quality

  24. Then and Now

  25. Then and Now continued…

  26. Ask us about our experiences… Panel Discussion

  27. Contact Us • Dan Rough: dan.rough@7digital.com • Hibri Marzook: hibri.marzook@7digital.com • Rob Bowley: rob.bowley@7digital.com • http://blogs.7digital.com/dev

More Related