Embed Size (px)
DESCRIPTION
All four Agile approaches in combination in one company! What a radical thought, especially with the fearsome flames of the agile methodology wars! It all started with Scrum versus Scrum. Then Scrum versus Kanban. Then everybody against DSDM. And finally late last year things escalated with the global take-up of the Scaled Agile Framework (SAFe). Sadly dogmatic Agilistas continue to see just one (or two) of the four approaches as the solution to everyones’ problems. Despite the fact that no single one can be the silver bullet. Yet despite this dogmatism, Agile and Lean has made a massive difference to people’s lives. Hundreds of thousands if not millions of IT professionals and hobbyists benefit daily from these approaches. So we must put our ego to one side and remember that the approaches are not about a particular methodology: They are about people and results. By putting people and results first we can illustrate in this session why, how and where all four approaches (Scrum, Kanban, SAFe & DSDM) are applicable. Incredibly we will see that a particular type of organization should consider all four! To support this discussion, we will examine different types of organization, each with their own set of characteristics. For each we will explore which approaches would be the most appropriate now and in the future plus risks.
Citation preview
Trifork Goto Night September 2014
Are you crazy? Using Scrum, Kanban,SAFe and DSDM in one Company!!!
Matthew Caine
AGILE
Some people call it amethod or an approach
above all
It is about PEOPLE and RESULTS
Assumptions
• You know something about “Agile”• You are looking for evidence that SAFe is or
may be not for you• You expect some quick-win “take-aways”• You need evidence that your transformation is
never finished
Who am I?• English• Come from near Liverpool / Manchester• I.T. background• Lived in CH since 1994• Worked in London, NY, Berlin, Geneva and ZH• Discovered “Agile” in 2009
August 2011Setup M.C. Partners & Associates
September 2012Launched the Agile Academy
Community
I Steal Ideas
Line Sorensen Rainer GrauBruno Heufelder
MichaelPolatos
KlausBucka-LassenMischa Ramseyer Steffen Lentz
Alan Moran
This is not Theory
Agile / LeaNManagement
Consulting
Agile / LeanManagement
Consulting
This is not Theory
The First Love…
The First Love…
But then …
In 2007…
In 2011…
In 2012…
http://kenschwaber.wordpress.com/2013/08/06/unsafe-at-any-speed/
Your Choice Today
So, which one?
A Quick Reminder
A Quick Reminder
A Quick Reminder
A Quick ReminderBusinessSponsor
BusinessVisionary
BusinessAnalysts
BusinessAmbass-
adors
BusinessAdvisors
Tech. Co- ordinator
SolutionTesters
SolutionDevs
ProjectManager
TeamLeader
Your Choice Today
So, which one?Based on what we knowThen apply that as our Silver Bullet
Considerations go Beyond Method
1. Who and where is the client?2. Fast continuous release cycle?3. Is your product delivered to a client?4. Is your product managed by you and offered as a
service?5. Do you have many teams and one product?6. Do you have many teams and many products?7. Do you have project managers, business analysts,
testers or organisational silos?8. What is the business model?
How dramatic do we want the culture change?
Software Vendors
Mobile Apps
Corporate IT
Digital Media
Characteristics of Digital Media
Examples• Homegate AG• www.NZZ.ch• ABB’s Website
Characteristics of Digital Media
Key CharacteristicsWho are the Clients External (with ABB, also internal) B2B & B2CProducts or Projects One concept but small products with short life-cyclesNr People / Teams 20-50 (3-7 teams)Business Model Subscriptions, visitors, advertising, marketing
Examples• Homegate AG• www.NZZ.ch• ABB’s Website
Digital Media: Which Approach?• Scrum (new development) / Kanban (defects)
– Product development– Need fast turn around– Low inter-team dependency risk– Proxy Product Owner is only option
• Why NOT SAFe– SAFe Planning & Release trains will slow down learning– Overheads of RTE, System Team, Epic Owner not needed
• Why Not DSDM– DSDM is a Project Method, not suitable to
product developmentIn the future SCRUM > KANBAN(Continuous delivery is slowed by sprints, planning is waste)
Digital Media: Which Approach?
Characteristics of Apps / Games
Characteristics of Apps / Games
Key CharacteristicsWho are the Clients External (but also internal) Usually B2CProducts or Projects Product based standalone mobile Apps & GamesNr People / Teams 5-50 (1-7 teams), with some games > 100 peopleBusiness Model Subscriptions, Download, Advertising, InApp Purchase,
Freemium
Apps / Games: Which Approach?• Scrum (new development) / Kanban (defects)
– Product development– Need fast turn around– Low inter-team dependency risk– Proxy Product Owner is only option
• Possibly SAFe for Large Products– Large Games can involved > 100 people (UX, Gameplay, Sound etc)– SAFe Planning & Release trains are Ok with a game > 9 months in development
• Why Not DSDM– DSDM is a Project Method, not suitable to
product developmentIn the future SCRUM > KANBAN(Continuous delivery is slowed by sprints, planning is waste)
Apps / Games: Which Approach?
?
Characteristics of Corporate IT
Examples• Allianz• Credit Suisse• Phonak• Diawa
Characteristics of Corporate IT
Key CharacteristicsWho are the Clients InternalProducts or Projects Many interconnected systems, “project” mentalityNr People / Teams 100 – 1000+Business Model Internal service
Examples• Allianz• Credit Suisse• Phonak• Diawa
Corporate IT: Which Approach?• DSDM (new development) / Kanban (defects)
– Projects!– Many stakeholders need managing– Governance needed (risk, financial, regulatory)– The end user is available and needs to be in the project team (no proxy!)– It is the closest true Agile approach to PMI and PRINCE2
• Why NOT Scrum– Cultural change too high– Greater risk of job insecurity (No business analyst, No project manager)– No guidance on governance– A Proxy Product Owner is waste
• Why Not SAFe– Not working on one product.– No governance in SAFe– Dean Leffingwell “Only suitable for environments with FLOW”
In the future > SAFe / Kanban?(Matrix Orgs & planning is waste)
Corporate IT: Which Approach?
Characteristics of Software Vendor
Key CharacteristicsWho are the ClientsProducts or ProjectsNr People / TeamsBusiness Model
Examples• Finnova• Avaloq• Bison• SAP
Characteristics of Software Vendor
Key CharacteristicsWho are the Clients External B2BProducts or Projects Highly integrated core-systems (banking, ERP etc)
Can take 12+ months to implement. UAT > 2 man-yearsNr People / Teams 150+ on one productBusiness Model License fees plus maintenance & support
Examples• Finnova• Avaloq• Bison• SAP
Software Vendor: Which Approach?
• SAFe (Core)– Product development– Delivery every 2-3 months– Many Teams– High inter-team dependency risk– Product Manager, Product Owners– Enterprise Architects
• “Value” streams need Scrum and Kanban
• Component teams need Kanban– They provide a “service” to the
“Value” teams so need to react to their needs.
Software Vendor: Implementation Projects?
• Need DSDM– DSDM is a Project Method– DSDM Lifecycle matches Sales-Process– Client is Embedded into the Project Team– Cadence of Scrum “Value” Streams (Release
Trains) and Project Teams can be synchronised.
Core Product Development: SAFe
All Four NeededAlignment of Cadence!
Component Team A: Kanban
Component Team B: Kanban
Foundation Phase
Implementation Projects: DSDM
Foundation Phase
IP IP
Rele
ase
Trai
nsSc
rum
IP
IP
IP
IP
Reviews / Demos
Software Vendor: Which Approach?
Discussion: How AboutConsulting Companies?
e.g. Deloitte, Accenture, Arvato-Systems, Liip, UNIC, Mimacom, Zühlke, BBV, TI&M etc
Characteristics?
Which Approach?
TODAY
Digital Media
Apps / Games
Corporate IT
Software Vendor
Consulting
?
Choose what fits theproblem and your culture and
consider all four methods!
Remember
Not so crazy afterall
Any Questions?
