Large scale project retrospectives from the trenches: An experience report from a big software company - Dr. Martin Engel and Christian Paulus ...
←
→
Page content transcription
If your browser does not render page correctly, please read the page content below
Public Large scale project retrospectives from the trenches: An experience report from a big software company Dr. Martin Engel and Christian Paulus, SAP SE Karlsruher Entwicklertag: Agile Day, 16.06.2016
Aboutt
44 years 310,000
of history and innovation customers in 190 countries 78,230
employees in 130+ countries
110 million And 100+ development centers
subscribers in our cloud
user base
Context: A large organization develops SAP Fiori
A large scale project retrospective in the UI technology development department — using Open Space
Open Space Technology as a format for
conducting a large scale Retrospective
Open Space Technology:
Invented by Harrison Owen in 1985.
Now being applied all over the world, with groups
from five to two thousand.
Very flexible format, that to a large extent
relies on self-organization in the group and
allows to efficiently discuss (and possibly solve)
complex questions and issues.
Preparation and plan
Preparation and plan
Preparation and plan
Preparation and plan
Preparation and plan
Preparation and plan
Preparation and plan
Open Space at work: Topics that were brought up
Open Space at work: Topics that were brought up
Open Space at work: Topics that were brought up
Open Space at work: Topics that were brought up
Open Space at work: Impressions
Open Space at work: Impressions
Open Space at work: Impressions
The 10 top topics from the retrospective
1. Salutogenic potentials of Scrum get
lost
2. Quality: What minimal quality
criteria do we always stick to?
3. Sustainability: Few long-term
decisions
4. Project management
5. Workload of employees
6. High communication effort
7. Why do we give up Scrum
methodology when the road gets
rocky?
8. Missing trust between PO and team
9. Team setup
10.Frequent priority changes on short
noticeFirst attempt at following-up
Surprise („Expect the unexpected“)
This was the plan: This was the unexpected outcome:Key learning: Align with all important stakeholders –
closely and early
Avoid: Try:
• Inform stakeholders about the plan
• Address concerns
• Adapt the plan together
(„Inspect and adapt“)
• Jointly decide about the adapted plan
Individually and before the first follow-
up meeting with all stakeholdersRestructuring: 10 topics 5 topics
Key learning: Stick to the topics as they are
brought forward in the Retrospective
Avoid: Aggregation of topics
Reduction of overlap of topics
Searching for synergy between topics
Try: Work on the topics as they were proposed in the RetrospectiveGroup work
Traction regained: From 5 problem statements to 5 solution proposals
Traction regained: From 5 problem statements to 5 solution proposals
Traction regained: From 5 problem statements to 5 solution proposals
Review of proposed solutions for the 5 topics
„Information & Communication“: Proposal: „AskMe“ concept
„Information & Communication“:
Proposal: „AskMe“ concept
The AskMe:
• your named information partner
• responsible for „his“ information
segment
• active information management:
collects information
distributes information
answers questions„Information & Communication“:
Proposal: „AskMe“ concept
The AskMe:
• your named information partner
• responsible for „his“ information
segment
• active information management:
collects information
distributes information
answers questions„Minimum Quality Criteria“ Proposal: Definition of a minimal set of RC, AC/DC, SC
„Minimum Quality Criteria“ Proposal: Definition of a minimal set of RC, AC/DC, SC
„Minimum Quality Criteria“ Proposal: Definition of a minimal set of RC, AC/DC, SC
„Minimum Quality Criteria“ Proposal: Definition of a minimal set of RC, AC/DC, SC
„Minimum Quality Criteria“ Proposal: An AC/DC Cook Book published in Wiki (covering also RC and SC)
„Minimum Quality Criteria“ proposal: Feedback in Review
„Minimum Quality Criteria“ proposal: Piloted and rolled
out as a standard for the whole UI department
Standardized in
Piloted in UI5 all of UI
Worked out a proposal for a
minimal set of quality criteria
in the UI area.Key success factor of the sub-project
„Minimal Quality Criteria“: Scoping & staffing
Scoping:
Well-defined scope
Narrow scope definition – don‘t try
to address and fix too much in parallel
Staffing:
All stakeholder types represented in
the (sub-) project team
(Sub-) project team: stable,
from α to Ω„Lean/Scrum in general and in ‚exceptional‘ cases“: Proposal: A Scrum Cook Book
„Lean/Scrum in general and in ‚exceptional‘ cases“: Cook Book sample entry on Retros and Cont‘s Improvement
„Lean/Scrum in general and in ‚exceptional‘ cases“: Cook Book sample entry on Retros and Cont‘s Improvement
„Lean/Scrum in general and in ‚exceptional‘ cases“: Project „Re-Launching Agile at UI“
„Lean/Scrum in general and in ‚exceptional‘ cases“: Project „Re-Launching Agile at UI“
„Lean/Scrum in general and in ‚exceptional‘ cases“:
Project „Re-Launching Agile at UI“
How do we
improve further?Key success factors of the sub-project „Lean/Scrum in general and in ‚exceptional‘ cases“ Key success factors: „Cook Book“ format as a template Careful selection of those proposals that you want to pilot and standardize Theory complemented with practical support to implement the theory.
Key success factors of a Retrospective:
The VAN principle
VAN: Vorbereitung
Abwechslung
NachverfolgungKey success factors of a Retrospective:
The PREVAIL principle
PREVAIL: PREparation
VArIation
FoLlow-upThank you! Questions?
Contact
Martin Engel works as a Development Project Expert in SAP's
User Interface Technology Development area.
Initially a C/C++ software developer and quality manager, in recent
years his focus has shifted to shaping the transition towards Lean
and Agile. He is a certified Scrum Master and started using agile
development methods back in 2006. He began applying Kanban in
his own team some eight years ago, in addition to supporting other
teams with training, coaching and mentoring. His current focus is
on shaping and supporting the scaled Lean/agile setup in the UI
development area.
Dr. Martin Engel
Certified Scrum Master und ISTQB Certified Tester (Advanced
Development Project Expert Level)
SAP SE
Products & Innovation − Technology − Design Thinking and Lean Startup coach
User Experience Platform − UI Core Services
Dietmar-Hopp-Allee 16, 69190 Walldorf Bikablo trainer
martin.engel@sap.com
© SAP 2016
© 2016 | 54
SAP SE or an SAP affiliate company. All rights reserved.
Martin Engel
Public 54Contact
Christian Paulus is a Development Manager for User Experience
Platform Core Services.
After joining SAP in 2002 as a Java Developer he worked in
different areas like Mobile Frameworks, Development Tools,
Business Process Management, Process Analytics and User
Interface Technology. In the past years he had several roles like
Developer, Project Manager, Scrum Master and Scrum Product
Owner.
As an “early adopter” of Lean and Agile in SAP one of his focus
topics was always continuous improvement inside teams and
Christian Paulus
organizations.
SAP SE
Products & Innovation − Technology −
User Experience Platform − UI Core Services
Dietmar-Hopp-Allee 16, 69190 Walldorf
c.paulus@sap.com
© SAP 2016
© 2016 | 55
SAP SE or an SAP affiliate company. All rights reserved.
Christian Paulus
Public 55You can also read
