why scrum cant fail

Why Scrum can not fail?

Understanding what is Scrum all about and how to adapt to it

Wednesday, 7 October, 2009

Andrea Tomasini

VP Professional Servicesandrea.tomasini@agile42.com

Andrea Tomasini

VP Professional Servicesandrea.tomasini@agile42.com

The Goal of Agile Approaches

Change from this... Production-based process

... to this. R&D based process

Thinking Lean - where Scrum comes from

The Lean Principles

Muri, mura, muda

Load(muri)

do not overload your

Processes

Flow (mura)

Flow (mura)keep the Flow

Waste (muda)

Waste (muda)remove non value adding

Activities

Eliminate waste What is waste in software?

Build quality in Do it right the first time round.

Create knowledge Amplify learning

Defer commitment Decide as late as possible

Deliver as fast as possible Learn as fast as possible

Respect people Empower the team

Optimize the whole Improve the entire system

Scrum Origin

• Scrum is a “Lean” approach to software development

Scrum Origin

• “Scrum” was first used by Toyota engineers at the Harvard Business Review, when they presented in 1986 the first idea of the Toyota Production System

Scrum Origin

• Jeff Sutherland and Ken Schwaber invented Scrum for Software Development (1995)

Scrum Characteristics

Teams choose the amount of work

Teams decide how to best reach the agreed goal

Work is prioritized based on Business Value

Allows to deliver working software at regular intervals

Adapts to change without big impact on development

Framework to control chaos (1/2)

• Based on the assumption that Software Development is not a defined process, and has to be controlled through empirical methods[1]... self organization, continuos inspection and adaption

1. Process Dynamics, Modeling and Control, Ogunnaike and Ray, Oxford University Press, 1992

• Scrum “encourages” the growth of fundamental values, that are stemming following simple practices on a daily basis, these values are

Transparency

Commitment

Transparency

Commitment

Courage

• Without these values the “self organization” and the “team collaboration” are not as effective as they could be...

Transparency

Commitment

Courage

Why Scrum works and why it can’t fail?

Why Scrum works? (1/2)

Time Box

The Scrum Approach tend to limit the complexity by creating a field in which for a specific timeframe the technology and the requirements can only slightly change

• The Lean approach let people closer to the problem make a decision on how to solve or avoid it, limiting the costs and continuously improving the process

• Self Organization of teams empower people and motivate them to achieve better results, having more fun, and delivering on time and with higher quality

• Organizations can change requirements at short defined interval, without affecting the productivity of the team, but having the chance to meet frequently customer expectations

• It allows to deliver working software at defined regular intervals

Why Scrum Can’t Fail?

• Scrum is a Framework that encourage and enable transparency, doing so by Empowering People into a work environment to autonomously make decisions in order to reach faster and more effectively a defined goal

• Empowered People will expose all the inefficiencies and impediments that are existing into the organization now, these impediments will have to be tackled and solved... or not

• Organizations that will not embrace the values of Lean and Scrum, won’t be able to successfully implement Scrum, and will fallback to “compromises” that will generate dysfunctions into the organization

“People and Organizations are failing Scrum, by not accepting to solve dysfunctions which Scrum will make

evident and clear, and hiding them behind ScrumBut(s)”

Leadership influences change

•“People don’t resist change. They resist being changed.” - Peter Senge

•“Culture does not change because we desire to change it. Culture changes when the organization is transformed; the culture reflects the realities of people working together every day.”- Frances Hesselbein

•“Faced with the choice between changing one’s mind and proving that there is no need to do so, almost everyone gets busy on the proof.” - John Kenneth Galbraith

Engagement

Realism

Engagement

Realism

Determination

Questions to ask yourself

•Do I clarify strategic direction?

•Do I strive for participation?

•Do I clarify expectations?

•Do I resolve conflicts?

Empowerment

How Often?

Questions? & Answers!

For any further comment and or question, feel free to contact us info@agile42.com

Further References:

Scrum Alliance: http://www.scrumalliance.orgControl Chaos: http://www.controlchaos.com

Implementing Scrum: http://www.implementingscrum.comJeff Sutherland Blog: http://jeffsutherland.com/scrum

Mike Cohn “User Stories”: http://www.mountaingoatsoftware.comagile42 Website: http://www.agile42.com/

why scrum cant fail

coach companies

flow mura

waste muda

load muri

lean principles muri

time round

productionbased process

goal of agile approaches

Documents

will sync genesis 22:1-17 anush john test results: fail,...

scrum round table devops & scrum

potters lea - redrow · 2019-02-18 · lea lea cant cant...

scrum - university of west...

scrum experience [o tutorial scrum]

why managers need scrum - scrum inc home - scrum inc · •...

online certiﬁed scrum professional scrum master...scrum...

applicant part a part b overall authorization to file...

can & cant

scrum at scale - scrum inc home - scrum inc · scaling the...

agile resiliency - better sw - broadswordsolutions · xp /...

scrum task allocation based on particle swarm...

scrum santhosh srinivasan. outline what is scrum what is...

scrum history , scrum force project & scrum injuries

agile-scrum. introduction to scrum sanil xavier what is...

catalogo formazione agile - inspearit...• scrum org psmi -...

the scrum guide - home | scrum guides of the scrum...

scrum 101: introduction to scrum

141015 discovering scrum at scrum roma

scrum for maximum awesome · © 2011 scrum inc. © 2014...