Projektharmonisierung bei der Haufe.gruppe

ASSESSMENT VON HP AGILE MANAGER ZUR
UNTERSTÜTZUNG DES GESAMTEN SOFTWAREENTWICKLUNGSZYKLUS
Dr. Eric Schmieder, 1.10.2014
Test Architect SW Quality Control
HP Software Anwendertreffen 2014
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. 1.300 Mitarbeiter in Freiburg (HQ), München, Berlin, St. Gallen u. Temeswar
• rd. 265 Mio € Umsatz
Seite 2
14.10.2014
Dr. Eric Schmieder, HAUFE.Gruppe
HAUFE.GRUPPE SWD QUALITÄTSKONTROLLE
In der SWD-Qualitätskontrolle eingesetzte Standardwerkzeuge von Hewlett-Packard:
ALM 11.52 - 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
14.10.2014
Dr. Eric Schmieder, HAUFE.Gruppe
HISTORICAL OVERVIEW
Wasserfall Model
V - Model
XP – Extreem Prog.
Agile Manifesto
1970 – Winston Royce
1979 - 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
14.10.2014
Dr. Eric Schmieder
SCRUM ELEMENTS - ARTIFACTS
Product Backlog - Wish List
› User Story/Use Case
› Prioritized
Sprint
Planning
Meeting
Sprint Backlog – Committed to do now
› When = Fixed dates
Backlog
Refinement
Meeting
› What = Product Backlog items
› How = List of tasks
Sprint
Retrospective
Meeting
Daily
Scrum
Sprint
Review
Meeting
Seite 5
14.10.2014
Dr. Eric Schmieder
HP AGILE MANAGER
Release Planning
Sprint Planning
Sprint Execution
Visibility
› Themes/Features
› Prioritizing user
stories
› Tasks definition
› Dashboard
› Monitoring and
Tracking
› ALI Reports
› Release Backlog
› Sprints
› Teams
Seite 6
14.10.2014
› Manage defects
› Manage team
capacity
Test Architect Team
› Closure/Done
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
14.10.2014
Dr. Eric Schmieder
AGILE TEAMS
Scrum Development Team
› Cross-functional group
› Attempt to build a
„potentially shippable product
increment „every Sprint“
› Collaborates
Product Owner
› Self-organizing
Scrum Master
Team Capacity
› Description
› Availability
› Velocity
Seite 9
14.10.2014
Dr. Eric Schmieder
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.
Seite 10
14.10.2014
Dr. Eric Schmieder
Good Visibility of the
progress for all parties
SPRINT BACKLOG MEETING
Product
Backlog
Lowest
Priority
Seite 11
14.10.2014
____________
____________
____________
____________
____________
____________
____________
____________
____________
____________
____________
____________
____________
____________
____________
Dr. Eric Schmieder
Release
Backlog
In Scope
Out Scope
› GUI is good overview
of the User Story
Sprint Backlog
Highest
Priority
› For each User Story,
tasks and acceptance
test are easily created
› Add comments and
sent email TIME
notifications
DAILY STANDUP MEETING
› Colors are used to
distinguish features
from bug fixes
› Simple and flexible
Drop and Drag
Recalculates progress
automatically
Seite 12
14.10.2014
Dr. Eric Schmieder
› Provide good visual
representations of
project activity
Simple increase/
reduce estimate
› Resemble the Post-it
note movement on a
white/wall board.
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
The team should discuss about
what went well and what could be
improved
Seite 13
14.10.2014
Dr. Eric Schmieder
Acceptance Criteria Statistics
Easy to measure that the
team goal was achieved
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.10.2014
Dr. Eric Schmieder
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
Agile Manager
HP ALM /QC
Releases and
User stories
sprints
Themes, features
Defects
and user stories
› Develop in Agile Manager; test in ALM
Defects
Seite 15
14.10.2014
Dr. Eric Schmieder
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
14.10.2014
Dr. Eric Schmieder
AGILE REQUIREMENTS MANAGEMENT
Requirement tree with a maximum of three levels (representing themes, features
and user stories).
Theme
Feature
User Story
Task & Acc. Criteria
Level
Business Process
Information Mode
Use Case
UI Mockup
Storyboard
who', 'what' and 'why'
to do & to check
Time Unit
Scale
Months
Product
Weeks
Days
Hours
Release
Sprint
Source: http://q1systems.com/?p=418
Seite 17
14.10.2014
Dr. Eric Schmieder
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
14.10.2014
Dr. Eric Schmieder
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
14.10.2014
Dr. Eric Schmieder
KONTAKT
Dr. rer. nat. Eric Schmieder
Lead Testarchitektur
[email protected]
Certified Project Manager (Project Management Institute, Inc.)
Certified Test Manager (International Software Testing Qualifications Board, Germany)
Stellenangebote: http://www.haufe-lexware.com/karriere

Download Report