Successfully reported this slideshow.

Visualization to the rescue - AgileByExample

0

Share

Upcoming SlideShare
Oasys style copy 6pk
Oasys style copy 6pk
Loading in …3
×
1 of 23
1 of 23

Visualization to the rescue - AgileByExample

0

Share

Download to read offline

Over the years PSI’s R&D department has struggled with delivering fix-price projects with long specification and little added value. We have tried many local optimizations but nothing has really changed the game. Since the beginning of 2015 we started to embrace NonBan, the process so lean that it does even not have a website. In fact, we completely changed the way we talk with our customers, plan project work and deliver the results. We have introduced the following agile/lean practices to help us:
• Single Responsibility Principle for requirements
• Epic -> Story -> Feature mapping
• Lead time as the main quality metric
• Multi-product roadmaps
• Value as the main driver instead of costs
• Progress visualization using JIRA Agile
Our journey is far from the end but it has already brought considerable benefits, or in worst case visualized problems everybody was talking about but noone had been able to pinpoint. We would like to show you what visualizing our old process has shown us and what kinds of solutions we were able to come up with.

Over the years PSI’s R&D department has struggled with delivering fix-price projects with long specification and little added value. We have tried many local optimizations but nothing has really changed the game. Since the beginning of 2015 we started to embrace NonBan, the process so lean that it does even not have a website. In fact, we completely changed the way we talk with our customers, plan project work and deliver the results. We have introduced the following agile/lean practices to help us:
• Single Responsibility Principle for requirements
• Epic -> Story -> Feature mapping
• Lead time as the main quality metric
• Multi-product roadmaps
• Value as the main driver instead of costs
• Progress visualization using JIRA Agile
Our journey is far from the end but it has already brought considerable benefits, or in worst case visualized problems everybody was talking about but noone had been able to pinpoint. We would like to show you what visualizing our old process has shown us and what kinds of solutions we were able to come up with.

More Related Content

Related Books

Free with a 14 day trial from Scribd

See all

Related Audiobooks

Free with a 14 day trial from Scribd

See all

Visualization to the rescue - AgileByExample

  1. 1. VISUALIZATIONto the rescue
  2. 2. 40products 30 000 000 lines of code
  3. 3. 777pages of (initial) specification „iterations” planned for the whole project partner of a construction company
  4. 4. 849 tasksin JIRA technical requirements
  5. 5. I have no value from a half-working power plant - actually how would it look like?
  6. 6. We know requirements - we are doing this business for 30 years.
  7. 7. Change request? We can discuss it during the steering committee.
  8. 8. I have planned 1 MEUR for IT projects this year - what can I have for that?
  9. 9. PJF why have we created it?
  10. 10. challenges
  11. 11. Customer Solutions ONE TECHNOLOGICAL PLATFORM PSIpenta PSItraffic PSImarket PSImetals PSIcommand the vision
  12. 12. the process PREPARATION IN COMMUNITY A Business Unit reports its business need in Community DEVELOPMENT PROJECT AK-Technik The need is discussed in community, new ideas come Managing Directors verify proposals before AK-T Agreed set of requirements is specified, estimated and turned into project proposal Decision Design document + acceptance by Community Programming + monthly status reports to Community Acceptance tests by Community
  13. 13. the process 7communities 60components over running migrationscustomer projects
  14. 14. problems
  15. 15. or symptoms?
  16. 16. improve quality
  17. 17. What is quality?
  18. 18. visualize your work
  19. 19. ? ! waste!
  20. 20. the real problems
  21. 21. the process PREPARATION IN COMMUNITY a Business Unit reports its business need in Community DEVELOPMENT PROJECT AK-Technik The need is discussed in community, new ideas come Managing Directors verify proposals before AK-T agreed set of requirements is specified, estimated and turned into project proposal Decision Setup the collaboration between RnD and first adopter Implementation in small increments, each immediately integrated into the product for validation Acceptance (based on real use in the product) NEW APPROACH
  22. 22. visualizehow you work metrics and needed changes will follow naturally

×