ASSESSMENT VON HP AGILE MANAGER ZUR UNTERSTÜTZUNG DES GESAMTEN SOFTWARE- ENTWICKLUNGSZYKLUS

Transcription

1 ASSESSMENT VON HP AGILE MANAGER ZUR UNTERSTÜTZUNG DES GESAMTEN SOFTWARE- ENTWICKLUNGSZYKLUS Dr. Eric Schmieder, Test Architect SW Quality Control HP Software Anwendertreffen 2014

2 FIRMENPORTRÄT Wir machen unsere Kunden erfolgreicher durch: Finanz-/Buchhaltungs-/Spezial-Software Digitale Arbeitsplatzlösungen (Fachinformationen, Wissensportale etc.) Webbasierte Services (Beschaffungsplattformen etc.) Fortbildungs- und Trainingsprogramme Haufe Gruppe: rd Mitarbeiter in Freiburg (HQ), München, Berlin, St. Gallen u. Temeswar rd. 265 Mio Umsatz Seite 2, HAUFE.Gruppe

3 HAUFE.GRUPPE SWD QUALITÄTSKONTROLLE In der SWD-Qualitätskontrolle eingesetzte Standardwerkzeuge von Hewlett-Packard: ALM Sprinter 12 - UFT 12 - QA Inspect - Performance Center -Rund 50 verschiedene HP ALM Projekte unterteilt in Desktop & Web Produkten -500 registrierte User, rund 70 Concurrent User Seite 3, HAUFE.Gruppe

4 HISTORICAL OVERVIEW Wasserfall Model V - Model XP Extreem Prog. Agile Manifesto 1970 Winston Royce Barry Boehm 1995 Kent Beck, Ward Cummingham and Ron Jeffries 2001 Ken Schwaber, Jeff Sctherland u.a. HP Test Directory. HP Quality Center v8.0 v10.0 HP ALM v11.00 v12.0 HP Agile Manager 2.0 Seite 4

5 SCRUM ELEMENTS - ARTIFACTS Product Backlog - Wish List User Story/Use Case Prioritized Sprint Backlog Committed to do now When = Fixed dates What = Product Backlog items How = List of tasks Sprint Retrospective Meeting Sprint Planning Meeting Backlog Refinement Meeting Daily Scrum Sprint Review Meeting Seite 5

6 HP AGILE MANAGER Release Planning Sprint Planning Sprint Execution Visibility Themes/Features Release Backlog Sprints Teams Prioritizing user stories Manage defects Manage team capacity Tasks definition Monitoring and Tracking Closure/Done Dashboard ALI Reports Seite Test Architect Team

7 RELEASE MANAGEMENT A Team can get up-and-running with the out-of-the-box version and quickly develop release plan. Set Test Default Capacity hours per day Set Storyboard Mode: Scrum Mode or Kanban Mode Seite 7

8 AGILE TEAMS Scrum Development Team Cross-functional group Attempt to build a potentially shippable product increment every Sprint Collaborates Self-organizing Team Capacity Description Availability Velocity Product Owner Scrum Master Seite 9

9 BACKLOG REFINEMENT MEETING The product backlog is a one dimensional (forceranked) list in priority order witch the product owner can reprioritize as more is learned. Good Visibility of the progress for all parties Seite 10

10 SPRINT BACKLOG MEETING Highest Priority Product Backlog Lowest Priority Release Backlog In Scope Out Scope GUI is good overview of the User Story Sprint Backlog For each User Story, tasks and acceptance test are easily created Add comments and sent TIME notifications Seite 11

11 DAILY STANDUP MEETING Colors are used to distinguish features from bug fixes Simple and flexible Drop and Drag Recalculates progress automatically Simple increase/ reduce estimate Provide good visual representations of project activity Resemble the Post-it note movement on a white/wall board. Seite 12

12 SPRINT REVIEW MEETING After a live demonstration of a potential shippable Committed PBI status product increment, simple report about what happened during the Sprint can be reviewed. Exploratory testing detected issue Acceptance Criteria Statistics The team should discuss about what went well and what could be improved Easy to measure that the team goal was achieved Seite 13

13 ALI SUMMARY Dashboards use data collected from the build and source code servers to provide information about the quality of releases and applications, builds and change sets: Logical thinking using statistical facts. Proper interpretation of statistical results Seite 14

14 HP AGILE MANAGER HP Agile Manager offers these key features: IDE integration and one button workspace provisioning Sync with HP QC/ALM Development and plan in Agile Manager; test in ALM Manage workload for both user Stories and defects in Agile Manager Develop in Agile Manager; test in ALM Agile Manager User stories Releases and sprints Themes, features Defects and user stories Defects HP ALM /QC Seite 15

15 AGILE PROJECT IN ALM ALM: Release/Cycle Agile M: Release/Sprint Release and cycle or sprint name must be identical. Release names must be unique in both endpoints. Target release for requirements must have a single target release in ALM. Seite 16

16 AGILE REQUIREMENTS MANAGEMENT Requirement tree with a maximum of three levels (representing themes, features and user stories). Level Time Unit Scale Theme Business Process Information Mode Months Product Feature Use Case UI Mockup Storyboard Weeks Release User Story who', 'what' and 'why' Days Sprint Task & Acc. Criteria to do & to check Hours Source: Seite 17

17 SCRUM ACCEPTANCE CRITERIA User stories has two part: Task Acceptance Criteria Project requirements is a thing demanded or obligatory (must User story # has n acceptance criteria. The relationship between acceptance criterion and requirement is n: m. The relationship between requirement and test case is again n: m. Thus: User Story #: n acceptance criterion n: m requirement n: m test case Seite 18

18 SUMMARY This tool certainly adheres to the Scrum methodology of agile software development (agilemanifesto.org), facilitating: Individuals and interactions over processes and tools with drag-anddrop interface and user friendly boards. Working software over comprehensive documentation with good visibility into tasks, metrics, and progress Customer collaboration over contract negotiation with the Built-in sprint closure and retrospective capabilities Responding to change over following a plan with the real-time feedback on progress. Seite 19

19 KONTAKT Dr. rer. nat. Eric Schmieder Lead Testarchitektur Certified Project Manager (Project Management Institute, Inc.) Certified Test Manager (International Software Testing Qualifications Board, Germany) Stellenangebote: