Agile Produktentwicklung in Kombination mit Scrum und V-Modell


Published on

Präsentation von Intland Software auf dem ""OBJEKTspektrum information day am 16. Mai in München

Published in: Technology
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Agile Produktentwicklung in Kombination mit Scrum und V-Modell

  1. 1. Agile Produktentwicklung in Kombination mit SCRUM und V-MODELL © 2011 Intland Software Janos Koppany & Michael Lukas Intland Software GmbH
  2. 2. Agenda <ul><li>V-Modell </li></ul><ul><li>Scrum </li></ul><ul><li>Scrum vs. V-Modell </li></ul><ul><li>Combination of Scrum and V-Modell in codeBeamer </li></ul><ul><li>What is codeBeamer </li></ul><ul><li>Scrum Wizard </li></ul><ul><li>Live Demo </li></ul>© 2011 Intland Software
  3. 3. V-Modell <ul><li>Key elements: </li></ul><ul><li>Process modules </li></ul><ul><li>Validation and Tracebility </li></ul><ul><li>Dependences between modules </li></ul><ul><li>Tasks that have to be executed </li></ul><ul><li>Iteration steps </li></ul>© 2011 Intland Software
  4. 4. Scrum <ul><li>Key elements: </li></ul><ul><li>User stories </li></ul><ul><li>Product Backlog </li></ul><ul><li>Sprints </li></ul><ul><li>Scrum Roles (Scrum Master, Product Owner, Team) </li></ul>© 2011 Intland Software
  5. 5. Scrum vs. V-Modell © 2011 Intland Software Scrum V-Modell <ul><li>Advantages </li></ul><ul><li>Light weighted </li></ul><ul><li>process/ project </li></ul><ul><li>management </li></ul><ul><li>Short iteration </li></ul><ul><li>cycles, Sprints </li></ul><ul><li>Easy to learn </li></ul><ul><li>Advantages </li></ul><ul><li>Clear definition of </li></ul><ul><li>project phases </li></ul><ul><li>Complete overview </li></ul><ul><li>about the whole </li></ul><ul><li>process </li></ul><ul><li>Industry-proven </li></ul><ul><li>Disadvantages </li></ul><ul><li>No overview about </li></ul><ul><li>the whole process </li></ul><ul><li>High communi- </li></ul><ul><li>cation effort (daily </li></ul><ul><li>Scrum) </li></ul><ul><li>Less architectural </li></ul><ul><li>overview </li></ul><ul><li>Disadvantages </li></ul><ul><li>Less flexibility </li></ul><ul><li>No clear Resource </li></ul><ul><li>disposition </li></ul><ul><li>Long iteration cycles </li></ul>
  6. 6. Combination of Scrum and V-Modell in codeBeamer <ul><li>In codeBeamer, the artecfacts of both methods are combined in one project - allowing to use the roles for Scrum and the defined roles in V-Modell. </li></ul>© 2011 Intland Software Requirements, Tasks, Test SCM, Builds, Project overview User Stories, Product Backlog, Sprint Plan, Kanban, Release In the release, all artifacts are combined together and give a complete overview about Scrum working items and V-Modell items. With Scrum Wizard, the team can decide which Sprints should belong to which release or version. With Scrum Wizard, the team can decide which Sprints should belong to which release or version.
  7. 7. codeBeamer <ul><li>What is codeBeamer? </li></ul><ul><li>codeBeamer is the award winning agile Application Lifecycle Management (ALM) solution for distributed software development. </li></ul><ul><li>codeBeamer provides agile planning, project management, knowledge management, document management, task, requirement and defect management, configuration management (ITIL), continuous build, version control, source code analysis and forums through a single and secure environment. </li></ul><ul><li>codeBeamer makes software development more agile, transparent and productive. </li></ul>© 2011 Intland Software
  8. 8. codeBeamer © 2011 Intland Software
  9. 9. Scrum Wizard © 2011 Intland Software
  10. 10. Product Backlog <ul><li>The product backlog is a high-level feature list that is maintained throughout the entire project. It aggregates descriptions of all potential features, prioritized as an absolute ordering by business value. In other words, it is “What” that will be built, sorted by importance. It is open and editable by anyone and contains rough estimates of both business value and development effort. </li></ul>© 2011 Intland Software
  11. 11. Sprint Plan <ul><li>The sprint backlog is the list of work the team must address during the next sprint. Features are broken down into tasks. With this level of detail the whole team understands exactly what to do. </li></ul>© 2011 Intland Software
  12. 12. Kanban Board <ul><li>Kanban , in Japanese means, loosely translated, 'card board'. In an agile system, Kanban is a method which uses virtual cards to represent issues to be resolved. A new feature is &quot;pulled&quot; into the product only when the work represented by an &quot;in progress&quot; card is completed. </li></ul>© 2011 Intland Software
  13. 13. Burndown Chart <ul><li>A burn down chart is a graphical representation of work left to do versus time. The outstanding work is on the vertical axis, with time along the horizontal. That is, it is a run chart of outstanding work. It is useful for predicting when all of the work will be completed. </li></ul>© 2011 Intland Software
  14. 14. Velocity Chart <ul><li>A velocity chart shows the sum of estimates of the work delivered across all iterations. Typically velocity will stabilize through the life of a project unless the project team make-up varies widely or the length of the iteration changes. As such, velocity can be used for future planning purposes. </li></ul>© 2011 Intland Software
  15. 15. LIVE DEMO <ul><li>LIVE DEMO </li></ul>© 2011 Intland Software
  16. 16. Thank you for your attention <ul><li>For further information please visit our homepage: </li></ul><ul><li> </li></ul><ul><li> </li></ul><ul><li>HgEclipse: http:// /project/HGE </li></ul><ul><li>codeBeamer Eclipse Studio: http:// /project/CBES </li></ul>© 2011 Intland Software