The document discusses the integration of agile product development with Scrum and the V-model, highlighting the key elements and advantages of both methodologies. It introduces Codebeamer as an agile application lifecycle management tool that facilitates project management by combining Scrum artifacts and V-model elements for enhanced transparency and productivity. The document also explains essential concepts like the product backlog, sprint plan, kanban board, and various charts used for project tracking.

1. Agile Produktentwicklung in Kombination mit SCRUM und V-MODELL © 2011 Intland Software Janos Koppany & Michael Lukas Intland Software GmbH

2. Agenda V-Modell Scrum Scrum vs. V-Modell Combination of Scrum and V-Modell in codeBeamer What is codeBeamer Scrum Wizard Live Demo © 2011 Intland Software

3. V-Modell Key elements: Process modules Validation and Tracebility Dependences between modules Tasks that have to be executed Iteration steps © 2011 Intland Software

4. Scrum Key elements: User stories Product Backlog Sprints Scrum Roles (Scrum Master, Product Owner, Team) © 2011 Intland Software

5. Scrum vs. V-Modell © 2011 Intland Software Scrum V-Modell Advantages Light weighted process/ project management Short iteration cycles, Sprints Easy to learn Advantages Clear definition of project phases Complete overview about the whole process Industry-proven Disadvantages No overview about the whole process High communi- cation effort (daily Scrum) Less architectural overview Disadvantages Less flexibility No clear Resource disposition Long iteration cycles

6. Combination of Scrum and V-Modell in codeBeamer 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. © 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. codeBeamer What is codeBeamer? codeBeamer is the award winning agile Application Lifecycle Management (ALM) solution for distributed software development. 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. codeBeamer makes software development more agile, transparent and productive. © 2011 Intland Software

8. codeBeamer © 2011 Intland Software

9. Scrum Wizard © 2011 Intland Software

10. Product Backlog 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. © 2011 Intland Software

11. Sprint Plan 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. © 2011 Intland Software

12. Kanban Board 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 "pulled" into the product only when the work represented by an "in progress" card is completed. © 2011 Intland Software

13. Burndown Chart 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. © 2011 Intland Software

14. Velocity Chart 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. © 2011 Intland Software

15. LIVE DEMO LIVE DEMO © 2011 Intland Software

16. Thank you for your attention For further information please visit our homepage: www.intland.com www.javaforge.com HgEclipse: http:// www.javaforge.com /project/HGE codeBeamer Eclipse Studio: http:// www.javaforge.com /project/CBES © 2011 Intland Software