Toolchain for agile teams: Traceability from product vision to working software Agile-Spain 2010 Madrid
© flioukas Haciendo  realidad la agilidad Toolchain for agile teams: Traceability from product vision to working software ...
mimacom | Facts and Figures <ul><li>Founded 1999 as a spin-off of the University of Applied Sciences Burgdorf </li></ul><u...
Myself… <ul><li>Head of Project Management </li></ul><ul><li>Scrum Master (CSM) </li></ul>21.05.11
Expectations? 21.05.11 Source:  http://www.stkyrans.com/images/angling.jpg
Today`s Roadmap <ul><li>Problems we had with interfacing different media & distributed teams </li></ul><ul><li>Our process...
How can that work remote or why use adaquate toos? 21.05.11 Source:  http://newsimg.bbc.co.uk/media/images/44181000/jpg/_4...
Scrum from Scratch <ul><li>History of our first Scrum-Project </li></ul>21.05.11 Scrum Initiative End 2007 2008 2009 2010 ...
[email_address] 21.05.11 3 – 6 WEEKS POTENTTIALLY SHIPPABLE PRODUCT INCREMENT Review Meeting SPRINT PLANNING MEETING 7 DAY...
mimacom Toolchain 21.05.11
Some of our Working Conditions <ul><li>Usually external Product Owner </li></ul><ul><li>Internal cross-functional Scrum De...
Project Map 21.05.11
Agile Legs & Manifesto <ul><li>Transparency </li></ul><ul><li>Inspection </li></ul><ul><li>Adaption </li></ul>21.05.11 Sou...
Artefacts | Product Backlog, Storyboards, … 21.05.11
Artefacts | Impediments <ul><li>Some of our big impediments were </li></ul><ul><li>No automated versioning </li></ul><ul><...
Product Backlog | Overview  21.05.11
Product Backlog | Requirement (i) 21.05.11
Product Backlog | Requirement (ii) 21.05.11
Product Backlog | Requirement (iii) 21.05.11
Product Backlog | Mockup 21.05.11
Release Planning 21.05.11
Sprint Backlog & Taskboard 21.05.11
Sprint Progress | Burndown 21.05.11
Sprint Progress | Issue 21.05.11
Sprint Progress | Source Code 21.05.11
QA | Code Reviews 21.05.11
QA | Testing 21.05.11
QA | Knowledge Base <ul><li>Use a Wiki! </li></ul>21.05.11
Collecting Data 21.05.11 Decisions Risks <ul><li>Product Backlog </li></ul><ul><li>Sprint Backlog </li></ul><ul><li>Releas...
Metrics | Burndown, Velocity, Risk 21.05.11
Meetings <ul><li>Tools we use for Daily Scrum, Review & Retrospective Meeting, Combat Testing and Story-Time Session </li>...
Wrap Up | Benefits 21.05.11 DONE Scope & Time Application Lifecycle Management Quality Assurance Costs Risks Transparancy ...
<ul><li>company www.mimacom.com ,  www.mimacomiberica.es   </li></ul><ul><li>mailto [email_address] </li></ul><ul><li>XING...
<ul><li>Customer-Oriented </li></ul><ul><li>User-Friendly </li></ul><ul><li>Competent </li></ul><ul><li>Qualitative </li><...
Upcoming SlideShare
Loading in …5
×

Toolchain for agile teams: Traceability from product vision to working software

1,198 views

Published on

Published in: Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,198
On SlideShare
0
From Embeds
0
Number of Embeds
6
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • 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 -&gt; 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.
  • Toolchain for agile teams: Traceability from product vision to working software

    1. 1. Toolchain for agile teams: Traceability from product vision to working software Agile-Spain 2010 Madrid
    2. 2. © flioukas Haciendo realidad la agilidad Toolchain for agile teams: Traceability from product vision to working software Joscha Jenni mimacom ag
    3. 3. mimacom | Facts and Figures <ul><li>Founded 1999 as a spin-off of the University of Applied Sciences Burgdorf </li></ul><ul><li>Specialised in JEE/Java development </li></ul><ul><li>Initiator and owner of edoras ® www.edorasware.org </li></ul><ul><li>Approximately 40 employees </li></ul><ul><li>Focus in development standards und project handling </li></ul><ul><ul><li>ISO-9001:2000 in TQMi since 6.6.2005 </li></ul></ul><ul><ul><li>HERMES: HSPTP and HSPM </li></ul></ul><ul><ul><li>Scrum: Certified Scrum-Master </li></ul></ul><ul><ul><li>ITIL: Certified Foundation </li></ul></ul><ul><ul><li>CMMI Scampi B September 2008 Level 3, Scampi A planed in Q3/2010 on level 5 </li></ul></ul><ul><li>Head office in Berne, offices in Zurich, Valencia, Rome, Stuttgart </li></ul>21.05.11
    4. 4. Myself… <ul><li>Head of Project Management </li></ul><ul><li>Scrum Master (CSM) </li></ul>21.05.11
    5. 5. Expectations? 21.05.11 Source: http://www.stkyrans.com/images/angling.jpg
    6. 6. Today`s Roadmap <ul><li>Problems we had with interfacing different media & distributed teams </li></ul><ul><li>Our process of coming to a solution </li></ul><ul><li>Advantages of using Scrum with a adaquate toolchain </li></ul>21.05.11
    7. 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
    8. 8. Scrum from Scratch <ul><li>History of our first Scrum-Project </li></ul>21.05.11 Scrum Initiative End 2007 2008 2009 2010 1st Scrum Offering 1st Sprint 2nd & 3rd Sprint 1st Release (13 Sprints) 2nd Release (16 Sprints) Felt Scrum-Improvement Time Usability Review
    9. 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
    10. 10. mimacom Toolchain 21.05.11
    11. 11. Some of our Working Conditions <ul><li>Usually external Product Owner </li></ul><ul><li>Internal cross-functional Scrum Development Team(s) & Scrum Master(s) </li></ul><ul><li>More & More international projects & distributed teams </li></ul>21.05.11
    12. 12. Project Map 21.05.11
    13. 13. Agile Legs & Manifesto <ul><li>Transparency </li></ul><ul><li>Inspection </li></ul><ul><li>Adaption </li></ul>21.05.11 Source: http://agilemanifesto.org/ Source: http://agilemanifesto.org/
    14. 14. Artefacts | Product Backlog, Storyboards, … 21.05.11
    15. 15. Artefacts | Impediments <ul><li>Some of our big impediments were </li></ul><ul><li>No automated versioning </li></ul><ul><li>No automated change history </li></ul><ul><li>More than one Backlog (reunite effort) </li></ul><ul><li>No proper Requirement Engineering & Management </li></ul><ul><li>No proper Release- & Sprintplanning </li></ul><ul><li>Problems to get automated metrics like Burndown & Velocity </li></ul><ul><li> No appropriate transparency, traceability and too much admin effort </li></ul>21.05.11
    16. 16. Product Backlog | Overview 21.05.11
    17. 17. Product Backlog | Requirement (i) 21.05.11
    18. 18. Product Backlog | Requirement (ii) 21.05.11
    19. 19. Product Backlog | Requirement (iii) 21.05.11
    20. 20. Product Backlog | Mockup 21.05.11
    21. 21. Release Planning 21.05.11
    22. 22. Sprint Backlog & Taskboard 21.05.11
    23. 23. Sprint Progress | Burndown 21.05.11
    24. 24. Sprint Progress | Issue 21.05.11
    25. 25. Sprint Progress | Source Code 21.05.11
    26. 26. QA | Code Reviews 21.05.11
    27. 27. QA | Testing 21.05.11
    28. 28. QA | Knowledge Base <ul><li>Use a Wiki! </li></ul>21.05.11
    29. 29. Collecting Data 21.05.11 Decisions Risks <ul><li>Product Backlog </li></ul><ul><li>Sprint Backlog </li></ul><ul><li>Releaseplanning </li></ul><ul><li>Sprintplanning </li></ul><ul><li>Taskboard </li></ul><ul><li>Impediment List </li></ul><ul><li>Burndown </li></ul><ul><li>Burnup </li></ul><ul><li>Velocity </li></ul><ul><li>Progress Reporting </li></ul><ul><li>Timetracking </li></ul><ul><li>Workload </li></ul><ul><li>Release Notes </li></ul><ul><li>… </li></ul>Changes Spikes Requirements User Stories Bugs Impediments Test Case Tasks Improvements Issues
    30. 30. Metrics | Burndown, Velocity, Risk 21.05.11
    31. 31. Meetings <ul><li>Tools we use for Daily Scrum, Review & Retrospective Meeting, Combat Testing and Story-Time Session </li></ul><ul><ul><li>Skype </li></ul></ul><ul><ul><li>Talkyoo </li></ul></ul><ul><ul><li>NetViewer </li></ul></ul><ul><ul><li>WebEx </li></ul></ul><ul><ul><li>GoToMeeting </li></ul></ul><ul><ul><li>… </li></ul></ul>21.05.11
    32. 32. Wrap Up | Benefits 21.05.11 DONE Scope & Time Application Lifecycle Management Quality Assurance Costs Risks Transparancy & Traceability
    33. 33. <ul><li>company www.mimacom.com , www.mimacomiberica.es </li></ul><ul><li>mailto [email_address] </li></ul><ul><li>XING www.xing.com/profile/Joscha_Jenni </li></ul><ul><li>LinkedIn ch.linkedin.com/in/joschajenni </li></ul>21.05.11 “ Well, you don‘t become a black belt by reading books. You have to work on it. Happy practicing.“ James Bach Source: http://www.uke.de/kliniken/psychiatrie/downloads/klinik-psychiatrie-psychotherapie/THANK_YOU_von_psd.jpg
    34. 34. <ul><li>Customer-Oriented </li></ul><ul><li>User-Friendly </li></ul><ul><li>Competent </li></ul><ul><li>Qualitative </li></ul><ul><li>Efficient </li></ul>… the open source integrator

    ×