Toolchain for agile teams: Traceability from product vision to working software
•
2 likes•1,060 views
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Toolchain for agile teams: Traceability from product vision to working software
Similar to Toolchain for agile teams: Traceability from product vision to working software (20)
Recently uploaded
Recently uploaded (20)
Toolchain for agile teams: Traceability from product vision to working software
- 1. Toolchain for agile teams: Traceability from product vision to working software Agile-Spain 2010 Madrid
- 2. © flioukas Haciendo realidad la agilidad Toolchain for agile teams: Traceability from product vision to working software Joscha Jenni mimacom ag
- 5. Expectations? 21.05.11 Source: http://www.stkyrans.com/images/angling.jpg
- 7. How can that work remote or why use adaquate toos? 21.05.11 Source: http://newsimg.bbc.co.uk/media/images/44181000/jpg/_44181384_eng_sa_scrum416.jpg
- 9. [email_address] 21.05.11 3 – 6 WEEKS POTENTTIALLY SHIPPABLE PRODUCT INCREMENT Review Meeting SPRINT PLANNING MEETING 7 DAYS RETROSPECTIVE MEETING 24H DAILY SCRUM 7 DAYS STORY TIME SESSION PRODUCT BACKLOG SPRINT BACKLOG COMBAT TESTING RELEASE PLANNING MEETING
- 14. Artefacts | Product Backlog, Storyboards, … 21.05.11
- 16. Product Backlog | Overview 21.05.11
- 17. Product Backlog | Requirement (i) 21.05.11
- 18. Product Backlog | Requirement (ii) 21.05.11
- 19. Product Backlog | Requirement (iii) 21.05.11
- 20. Product Backlog | Mockup 21.05.11
- 22. Sprint Backlog & Taskboard 21.05.11
- 23. Sprint Progress | Burndown 21.05.11
- 24. Sprint Progress | Issue 21.05.11
- 25. Sprint Progress | Source Code 21.05.11
- 26. QA | Code Reviews 21.05.11
- 27. QA | Testing 21.05.11
- 30. Metrics | Burndown, Velocity, Risk 21.05.11
- 32. Wrap Up | Benefits 21.05.11 DONE Scope & Time Application Lifecycle Management Quality Assurance Costs Risks Transparancy & Traceability
Editor's Notes
- If too many: Project leader? Scrum Master? It-manager? Product Owners? Tester? Developer? System-administrator? Others?
- Content questions @ the end, i had to bring the session down from 90 to 60 minutes If you do not understand my english, interrupt me
- Usually external Product Owner: Fixed Price Projects, Project Service , no product development company
- It is how to drive a bycicle when you are somewhere and you know after 5 minutes where you are. You can`t take a new way because you have no clue where you are. Manually synchronization -> big time effort, costs money
- If you move quickly you must have a basic repository where all people have access not loss time. How to improve if you don`know wher you are
- Online Backlog Describe Columns
- Automated Versioning of protocols, documents
- i`m around tomorrow, let me know if you have a question.