ralph jocham, effective agile - scaled scrum at swiss postal services | agile greece summit 2015
TRANSCRIPT
9/22/15
1
10 Months, 7 Teams, 18 Apps
Scaled Scrum atSwiss Postal Services
Ralph Jocham, effective agile.
12 Months, 7 Teams, 22 Apps
Scaled Scrum atSwiss Postal Services
Ralph Jocham, effective agile.
9/22/15
2
Ø Started as programmer;; discovered process as a problem early onØ First Unified Process with UML Ø Agile since 2000, Scrum since 2003Ø Did come around, different cultures and domainsØ Founder of effective agile. Ø Trainer with
Ralph Jocham+41 79 448 6388
3
effective agile. 4
9/22/15
3
Background
• end of life• 1 system with hardware Dependency• 1 vendor• 2 releases per year• many, many needs
effective agile. 5
History
effective agile. 6
2003 – 2005 *
8‘400
PPT2800(as of today ~3‘500
in use)
2007 – 2011 *
18‘000
Skeye.Allegro LS(all in use)
2013 – 2015 *
22‘000
(example devices)
* Provisioning Period
1999 – 2004 *
Unknown number
9/22/15
5
Good decision 1
effective agile. 9
RFP (request for proposal) based on skills and not requirements
Good decision 2
effective agile. 10
9/22/15
6
Roles, Artifacts and Events in Action
RolesProduct OwnerDevelopment TeamScrum Master
ArtifactsProduct BacklogSprint BacklogIncrement
EventsSprint PlanningSprintDaily ScrumSprint ReviewRetrospective
Product Backlog
Sprint Planning Meeting
Sprint Backlog Sprint
Increment
Review
Retrospective
Daily Scrum
ScrumMaster
(source: ADM)
Potentially Releasable
effective agile. 11
1 Project
1 Scrum Team
Easy1 Product
effective agile. 12
9/22/15
7
1 Project
n Scrum Team
OK1 Product
effective agile. 13
effective agile. 14
Program ManagerPortfolio Manager
Enterprise ScrumMaster
Enterprise QA
Enterprise Architect
PO 1 PO 4PO 2 PO 3 TPL Backend
Domain SME PM (PostMail)
Domain SME PM(PostLogistics)
Domain SME PM (Poststell. & Ver.)
Namics Unisys Adesso Netcetera Erni IBM IT Post IT Post
Domain
9/22/15
8
n Project
n Scrum Team
?n Product
effective agile. 15
App 3
App 2
App 1
App n
…PortfolioOwner
12/2013 01/2014 01/2015
App 3
App 2
App 6
App 5
Architecture/Infra/Platform
Ap p 8
A/I/P
…
Arch itectu re / In frastru ctu re / P latfo rm
App 1 App 4 App 7
App 2 4
App 23
App 2 2
App 1 0
App 9
App 1
Product Owner
US1US2US3US4…US n
Product Backlog
Use Case X
X O n e
[ ] Tw oX Th ree
+ Fo u r
X O n e
[ ] Tw oX Th ree
+ Fo u r
X O n e
[ ] Tw oX Th ree
+ Fo u r
X O n e
[ ] Tw oX Th ree
+ Fo u r
X O n e
[ ] Tw oX Th ree
+ Fo u r
X O n e
[ ] Tw oX Th ree
+ Fo u r
US 1US 2US n
App PortfolioBurndown
Arch/ Infra/Platform -‐ Clear Acceptance Criteria-‐ Estimated-‐ Specified with Examples per case
App Product BacklogBurndown
Week 1 Week 2
A3 ReportEvery Sprint
One Definition of Done-‐ Engineering Practices, Coding Standards-‐ Required Tests and Test Coverage-‐ Architecture / Infrastructure-‐ Documentation
Enterprise Scrum Master
Sprint BacklogBurndown
Week 1 Week 2
QV
Scrum Master
US1
US2
US3
PBI Open Dev Done
Definition of DoneAcceptance CriteriaARE 100% FULLFILLED
Review Retro
Enterprise Architect
Agile Tester
Programmer
Architect
ProgrammerProgrammer
Programmer
Development Team
Fachlicher Teilprojekteiter, AV, FV
BA
Agile Tester
effective agile. 16
9/22/15
9
Scrum
Sprint Length: 2 weeksProduct Backlogs: 1 per AppScrum Tool: JiraDocumentation: ConfluenceContinuous Integration: JenkinsTest Automation: JUnit, Selenium, Appium (Docker) Reporting: effective agile. A3 Report
Classic Scrum with additional exchanges for Scrum of Scrums
Exchanges:-‐ Alignments (allow emergence for competing concerns)-‐ Demo (Birds eye overview, very quick empowered decision making)-‐ World Cafes as needed
Sprint
effective agile. 17
Good decision 3
effective agile. 18
2 Weeks
9/22/15
11
Good decision 4
effective agile. 21
Monday FridayWednesday ThursdayTuesday0800
1800
12001300
Review
Retropublic-‐Demo Part 1Sprint
Planning 2public-‐Demo Part 2
Sprint Planning 2
Sprint n+1
Sprint Planning 1
Sprint Planning 1
RetroReview
BA/RE Alignement
ARCH Alignement
SM Alignement
1 Product Owner, 2 Scrum Teams
QA Alignement
9/22/15
12
Definition of Done• Implemented• Committed• Compliant to development standards• Passes statically code analysis• Documented (Scenario, Use Case, SAD, Test Case, Interfaces)• Reviewed within the Scrum Teams;; this is a responsibility of the Scrum Team• automatic Unit Tests (for none UI, i.e. tier containing business logic has a test coverage
of 90% or higher)• automatic Selenium Tests;; each scenario has at least one Selenium test• automatic AppiumTests on target device• Maven Build Profile (POM.xml)• Jenkins Build Job is up to date and compiles, tests, analyses the existing and newly
added code• All texts are I18N• No known bugs are existing
Only Product Backlog items which fulfill the Definition of Done are being reviewed in the Sprint Review
effective agile. 23
9/22/15
14
effective agile. 27
Namics
Unisys
Erni
IBM
netcetera
IT Post
Common
ContinuousIntegration /
Office
Common/ Office
CoffeeAdesso
9/22/15
15
Start
Very first Sprint January 8th 2014
effective agile. 29
… by the way …
We won’t know for another 8 months on which device the system has to work another 8 months
effective agile. 30
9/22/15
16
Very bad decision
… or assumption
BACKENDS WILL BE READY
effective agile. 31
effective agile. 32
9/22/15
21
APPS 27 # 22SCHEDULE18 # 12BUDGET ?QUALITY CTEAM ? # C
effective agile. 41
Q & A
effective agile. 42
Scaled Scrum atSwiss Postal Services
+41 79 448 6388@rjocham