Cas2010 toolchain-for-agile-teams-traceability-from-product-vision-to-working-software
•
0 likes•498 views
The document discusses the use of an agile toolchain at mimacom to improve traceability and transparency from product vision to working software. Some key challenges included a lack of integrated versioning, change history, and metrics collection across multiple disconnected tools. mimacom implemented Scrum processes along with an integrated toolchain including a product backlog, taskboard, burndown charts, and code review tools to improve visibility, coordination for distributed teams, and collect metrics to measure progress.
More Related Content
Viewers also liked
Viewers also liked (17)
Similar to Cas2010 toolchain-for-agile-teams-traceability-from-product-vision-to-working-software
Similar to Cas2010 toolchain-for-agile-teams-traceability-from-product-vision-to-working-software (20)
More from Agile Spain
More from Agile Spain (20)
Recently uploaded
Recently uploaded (20)
Cas2010 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 © mimacom ag
- 2. Haciendo realidad la agilidad Toolchain for agile teams: Traceability from product vision to working software © flioukas Joscha Jenni mimacom ag © mimacom ag
- 3. mimacom | Facts and Figures • Founded 1999 as a spin-off of the University of Applied Sciences Burgdorf • Specialised in JEE/Java development • Initiator and owner of edoras® www.edorasware.org • Approximately 40 employees • Focus in development standards und project handling ISO-9001:2000 in TQMi since 6.6.2005 HERMES: HSPTP and HSPM Scrum: Certified Scrum-Master ITIL: Certified Foundation CMMI Scampi B September 2008 Level 3, Scampi A planed in Q3/2010 on level 5 • Part of a Europe-wide acting group of companies with circa 150 employees • Head office in Berne, offices in Zurich, Valencia, Rome, Stuttgart © mimacom ag 09.06.2010 3
- 4. Myself… • Head of Project Management • Project Leader • Scrum Master (CSM) © mimacom ag 09.06.2010 4
- 5. Expectations? Source: http://www.stkyrans.com/images/angling.jpg © mimacom ag 09.06.2010 5
- 6. Today`s Roadmap • Problems we had with interfacing different media • Our process of coming to a solution • Advantages of using Scrum with a adaquate toolchain © mimacom ag 09.06.2010 6
- 7. How can that work remote or why tooling? Source: http://newsimg.bbc.co.uk/media/images/44181000/jpg/_44181384_eng_sa_scrum416.jpg © mimacom ag 09.06.2010 7
- 8. Scrum from Scratch History of our first Scrum-Project Felt Scrum-Improvement Improvement Time End 2007 2008 2009 2010 © mimacom ag 09.06.2010 8
- 9. Scrum@mimacom 24H BUILD 7 DAYS 3 – 6 WEEKS 7 DAYS TEST PLAN IMPROVE © mimacom ag 09.06.2010 9
- 10. mimacom Toolchain © mimacom ag 09.06.2010 10
- 11. Project Map © mimacom ag 09.06.2010 11
- 12. Some of our Working Conditions • Usually external Product Owner • Internal cross-functional Scrum Development Team(s) & Scrum Master(s) • More & More international projects & distributed teams © mimacom ag 09.06.2010 12
- 13. Agile Legs & Manifesto • Transparency • Inspection • Adaption Source: http://agilemanifesto.org/ Source: http://agilemanifesto.org/ © mimacom ag 09.06.2010 13
- 14. Artefacts | Product Backlog, Storyboards, … © mimacom ag 09.06.2010 14
- 15. Artefacts | Impediments Some of our big impediments were • No automated versioning • No automated change history • More than one Backlog (reunite effort) • No proper Requirement Engineering & Management • No proper Release- & Sprintplanning • Problems to get automated metrics like Burndown & Velocity No appropriate transparency, traceability and too much slack © mimacom ag 09.06.2010 15
- 16. Product Backlog | Overview © mimacom ag 09.06.2010 16
- 17. Product Backlog | Requirement (i) © mimacom ag 09.06.2010 17
- 18. Product Backlog | Requirement (ii) © mimacom ag 09.06.2010 18
- 19. Product Backlog | Requirement (iii) © mimacom ag 09.06.2010 19
- 20. Product Backlog | Mockups © mimacom ag 09.06.2010 20
- 21. Collecting Data • Product Backlog Sprint Backlog Issues • • Releaseplanning • Sprintplanning Decisions • Taskboard User Stories • Impediment List Test Case • Burndown Impediments Changes • Burnup Risks • Velocity Tasks • Progress Reporting Bugs Spikes • Timetracking Improvements • Workload Requirements • Release Notes • … © mimacom ag 09.06.2010 21
- 22. Release Planning © mimacom ag 09.06.2010 22
- 23. Sprint Backlog & Taskboard © mimacom ag 09.06.2010 23
- 24. Sprint Progress | Burndown © mimacom ag 09.06.2010 24
- 25. Sprint Progress | Issue © mimacom ag 09.06.2010 25
- 26. Sprint Progress | Source Code © mimacom ag 09.06.2010 26
- 27. QA | Code Reviews © mimacom ag 09.06.2010 27
- 28. QA | Testing © mimacom ag 09.06.2010 28
- 29. QA | Knowledge Base Use a Wiki! © mimacom ag 09.06.2010 29
- 30. Metrics | Burndown, Velocity, Risk © mimacom ag 09.06.2010 30
- 31. Meetings • Tools we use for Daily Scrum, Review & Retrospective Meeting, Combat Testing and Story- Time Session Skype Talkyoo NetViewer WebEx GoToMeeting … © mimacom ag 09.06.2010 31
- 32. Wrap Up | Benefits DONE © mimacom ag 09.06.2010 32
- 33. Source: http://www.uke.de/kliniken/psychiatrie/downloads/klinik-psychiatrie- psychotherapie/THANK_YOU_von_psd.jpg company www.mimacom.com, www.mimacomiberica.es mailto joscha.jenni@mimacom.com XING www.xing.com/profile/Joscha_Jenni LinkedIn ch.linkedin.com/in/joschajenni © mimacom ag 09.06.2010 33
- 34. Customer-Oriented User-Friendly Competent Qualitative Efficient …the open source integrator © mimacom ag 34