8 lessons learned from becoming agile 15.5.2010 ESTONIA Marko Taipale.

Slides:



Advertisements
Similar presentations
ATMAN HB summary seminar # Challenges 2 ATMAN project 9/17/2010.
Advertisements

Lean Startup Presented by:
387 Million Ways For a Startup to Fail… and How to Avoid Them Steve Blank Twitter: sgblank.
7 Deadly Agile Sins of a Startup Company. Pride Opportunity Cost: Learn how and when to effectively say “No” to the business. Under promise, over deliver.
Steve Collins Richland County IT Manager Agile.  Have Fun  Learn About Agile  Tell Some Stories.
Archana Mehta. Spot a Failing project Costs a lot more than it should Its takes longer than anyone expected The product doesn’t do what it was supposed.
What is Agile? Agile is a software methodology based on iterative and incremental development, where requirements and solutions evolve through collaboration.
Entrepreneurship Start, Survive and Grow Dr. Travis Perera Postgraduate Institute of Management
NAUG NAUG Knowledge Evening – th February 2007.
Non-Coding Activities a Development Team Needs a.k.a ”I don’t code, am I no longer useful?” Maaret Pyhäjärvi| | Twitter: maaretp Test Granlund.
The Five Dysfunctions of a Team What do I need to do and to avoid in order to get the most out of my team?
Lean Software Development Tips and Tricks Augusto “Gus” Evangelisti - PaddyPower PLC
Computer Engineering 203 R Smith Agile Development 1/ Agile Methods What are Agile Methods? – Extreme Programming is the best known example – SCRUM.
Paweł Słowikowski What can Agility do for YOU. Who am I Have been: Software tester Verification Project Manager Scrum Master Agile Coach Currently: Scrum.
CS3500 Software Engineering Agile Software Development (1) Agile software development, proposed in 2001 by the non-profit Agile Alliance, has four basic.
7 Sins of Scrum and other Agile Anti-Patterns Todd Little VP Product Development June 2015.
Agile Methodologies for Project Management By – Komal Mehta.
“It’s not our differences that divide us, it’s our judgments about each other that do.” (Meg Wheatly)
Monster-Sized Agile Adoptions SUCCESS AND FAILURE STRATEGIES.
Agile Software Development What is Agile? And How are we implementing Agile?
THE THREE THINGS You Need to Know to Transform Any Sized Organization into an Agile Enterprise.
Larry Apke Agile Expert
Alcatel-Lucent CDC Workshop, Coaching & Knowledge Transfer Project Management.
1 מודל ניהול הצוותים של MSF. 2 Causes of failure  Poorly-defined objectives  Insufficient planning  Lack of executive support  Organizational barriers.
Process is continuously improving Have Definition of Done (DoD) DoD achievable within each iteration Team respects DoD The bottom line Delivering working,
Prototyping a High Quality Student Employee Cameron Goble Technical Training Consultant.
AP-1 5. Project Management. AP-2 Software Failure Software fails at a significant rate What is failure? Not delivering it on time is an estimation failure.
SCRUMBAN?!?! What is it and how can it help your team?
Everyone Communicates Few Connect
When you are Agile you get Lean How Agile reduces waste in software develpment.
AP-1 4. Agile Processes. AP-2 Agile Processes Focus on creating a working system Different attitude on measuring progress XP Scrum.
Agile Information Management Development. Agile Project Management Characteristics  Acceptance and even welcome of changing requirements  Incremental.
Growing and Sustaining An Offshore Scrum Engagement Edward Uy & Nikos Ioannou Kelley Blue Book.
Bringing Sense, Sensibility, and Sanity to projects.
Theories of Agile, Fails of Security Daniel Liber CyberArk.
Trust, Ownership and Motivation. Contents Trust, Ownership & Motivation How does it feet to be Trusted? What Trust Looks Like What must you do to be Trusted?
Project management methodologies Waterfall vs. agile vs. half-arsed agile.
LEAN START UP. The way things used to be … Write a business plan Pitch your business to investors Assemble a team Introduce your product Sell, sell, sell.
1 confidential | ©2015 Sabre GLBL Inc. All rights reserved. Implementing Kanban at Different Levels During Agile Adoption Krishnakumar C Principal Agile.
Lean Software Development (Can Çetin)
Phoenix Scrum User Group Simplifying Scrum Online May 21 st 2009.
It’s Agile …. like! A Corkman’s introduction to Agile software delivery.
The Kiev Experiment Evolving Agile Partnerships. Who are we? Simon Sasha Peter.
Lean Software Management: BBC Worldwide Case Study EECS811: IT Project Management Case Study Cody Mock February 8, 2016.
Leffingwell et al. © 2015 Scaled Agile, Inc. All Rights Reserved 1 Foundations of the Scaled Agile Framework ® Values, Principles, Practices, Implementation.
Disciplined Agile Takes the Mystery Out of Agile Software development is inherently complex The Disciplined Agile (DA) framework describes how: – Agile.
Introduction to Agile. Introduction Who is this guy?
Kanban Advanced Software Engineering Dr Nuha El-Khalili.
Benjamin Day Get Good at DevOps: Feature Flag Deployments with ASP.NET, WebAPI, & JavaScript.
Collaborative leadership workshop Accelinnova.com/pdtclassdev.html.
Agile Methodology. -Dhanashree Kumkar -Plus91 Technologies.
Informed Traveler Program and Applications Agile / Scrum Overview Jerry Inberg.
Agile in the Wild The many ways to Apply Agile (not just Scrum and Kanban)
7 Sins of Scrum and other Agile Anti-Patterns
Transforming the World of Work? Or Confusing It?
Agile Training - Kanban
Real Metrics for Real Decisions
By: By: Agile Scrum Master Online Training.
Lean Startup “Taking a scientific approach to building a company”
© The Table Group. All Rights Reserved.
Johanna Rothman Create Technical Excellence Chapter 9
Johanna Rothman Agile Team Measurements Chapter 12
How to Successfully Implement an Agile Project
Phillip Steele Software Development Team Lead Sage
Introduction If you have got a call for an Agile testing interview, then congratulations are in order. You may be feeling nervous, but it sure to be felt.
Proof of Concept By Peter Baskerville 20/07/2019.
The lean startup –Eric Ries
Avoidance of ACCOUNTABILITY
Enterprise Business Agility Transformation What it takes to start and to scale Andrea Willemse EBA Summit Atlanta Sept 11-12, 2019.
Product Development & Planning
Presentation transcript:

8 lessons learned from becoming agile ESTONIA Marko Taipale

Visited 13 companies Coached 2 agile transitions and 10+ teams Co-founded 1 Lean startup Trained over 300 people

Failed enough to tell stories Succeeded enough to show results

1. Why do you want to be agile ? 2. How to reach business agility ? 3. Organization as a people system

1. Why do you want to be agile ? (Being = respect the values and principles)

80% had no goal for being agile no method to reach the goal … no way to measure if they were getting any better

No Goal – No chance to Score

Lesson #1 Set a goal for being agile, otherwise you achieve nothing (It’s ok to figure it out...)

“What does method X say about Y?”

“What does method X say about Y?” Collaborate!

Lesson #2 Commit to agile values and principles; your practices will follow Craft your own process

Pilot, Scale, Optimize

Pilot, Scale, Optimize

Pilot, Scale, Optimize OR 1)Visualize the value stream 2)Fix the way you manage product development 3)Continuous Improvement

Pilot, Scale, Optimize OR 1)Visualize the value stream 2)Fix the way you manage product development 3)Continuous Improvement Multiple ways so what’s the point?

Pilots are not about proving if agile works Forward motion is often thought as progress

Lesson #3 Pilot is about learning …not “working software” … not about getting results Continuous Improvement

Make the cycle as short as possible

A way of learning 5 whys There are no technical problems only human problems

Lesson #1 You need to have a SMART goal Lesson #2 Commit to agile values and principles; your practices will follow Lesson #3 Progress is about learning

2. How to reach business agility ?

”Agile teams need to value adaptability over predictability ” - Someone in Twitter

Lesson #4 Business agility is about having adaptability and predictability - My experience

” Where do I get the backlog?” what to build

“No plan survives first contact with the customers” - Steven Blank

Customer Discovery Customer Validation Customer Creation Scale Company Customer Development

Customer Discovery Customer Validation Customer Creation Scale Company Agile Product Development Agile Product Development Data, feedback, Insights Hypotheses, experiments, insights Customer Development

Customer Discovery Customer Validation Customer Creation Scale Company Agile Product Development Agile Product Development Data, feedback, Insights Hypotheses, experiments, insights Customer Development Problem Team Solution Team

“Should I do whatever my customers want me to do?”

Lesson #5 Create product vision and validate it with customer development Vision = a boundary for her wishes

Is agile about delivering features as fast as possible?

Who cares about velocity? We can work on highest priority story – who cares? Nr 1 waste = Unused features Building a feature maybe the wrong answer

It is not about how much but rather how little you can release M inimum V iable P roduct

Lesson #6 Find your Minimum Viable Product It should make you feel embarrassed

“It's the things that are not there that we are most proud of"

Lesson #4 Business agility is about having adaptability and predictability Lesson #5 Create product vision and validate it with customer development Lesson #6 Find your Minimum Viable Product

3. Organization as a people system

”We have Scrum but we are still slow!”

Development Design Customer approval Internal approval Idea ResourcingDeployment

Development 2m Design 1m Customer approval 2h Internal approval 2h Idea Resourcing 1d Deployment 3w

Development 2m 15 Design ready 6m 1w Design 1m Customer approval 2h 2d Internal approval 2h Idea 6m Resourcing 1d 8 Selected ideas Deployment 3w 12 Production ready 6m

Development 2m 15 Design ready 6m 1w Design 1m Customer approval 2h 2d Internal approval 2h Idea 6m Resourcing 1d 8 Selected ideas Deployment 3w 12 Production ready 6m SCRUM!

Development 2m 15 Design ready 6m 1w Design 1m Customer approval 2h 2d Internal approval 2h Idea 6m Resourcing 1d 8 Selected ideas Deployment 3w 12 Production ready 6m SCRUM!

Optimize the whole Lesson #7 Beware sub-optimization Visualize the value stream Identify bottleneck Limit WIP on all levels Incentives are bad!

Adoption is about letting problems to surface Manage the system, remove chance for failure, make it flow

Smell: The fear of being vulnerable Leader: Go First

Smell: The fear of being vulnerable Leader: Go First Smell: The desire to preserve artificial harmony Leader: Mine for Conflict

Smell: The fear of being vulnerable Leader: Go First Smell: The desire to preserve artificial harmony Leader: Mine for Conflict Smell: The lack of clarity or buy-in Leader: Force Clarity and Closure

Smell: The fear of being vulnerable Leader: Go First Smell: The desire to preserve artificial harmony Leader: Mine for Conflict Smell: The lack of clarity or buy-in Leader: Force Clarity and Closure Smell: The need to avoid interpersonal discomfort Leader: Confront Difficult Issues

Smell: The fear of being vulnerable Leader: Go First Smell: The desire to preserve artificial harmony Leader: Mine for Conflict Smell: The lack of clarity or buy-in Leader: Force Clarity and Closure Smell: The need to avoid interpersonal discomfort Leader: Confront Difficult Issues Smell: The pursuit of individual goals and status Leader: Focus on Collective Outcomes

Lesson #8 Build great teams

I help companies to improve by showing what I have done how I have done it and what I have learned about it. I am a CTO of a lean startup Marko huitale.blogspot.com

1.Why do you want to be agile ? L1: Set a goal for being agile or you achieve nothing L2: Commit to agile values and principles; your practices will follow L3: Piloting is learning. Learning is progress. 2. How to reach business agility ? L4: Business agility is about having adaptability and predictability L5: Create product vision and validate it with customer development L6: Find your Minimum Viable Product 3. Organization as a people system L7: Optimize the whole L8: Build great teams

Photo credits Flickr users