Agile and Scrum for Executives

Copyright © 2013-2015 ScrumArabia. Portions used with permission. All rights reserved 1

Intro To Agility And Scrum For Executives

V30, June 2016

Joanna El-Khoury, ASM, [email protected]


About Joanna

12 years of experience as project manager, team leader and consultant.

Agile Transformation Agent, Trainer & Coach.

Computer Science and MBA.

Agile Business Consultant, Culture Modifier and Coach at Scrum Arabia


Agenda

Challenges faced by projects

Introduction to Agility and Scrum

The Scrum Framework

Who did it already

Proposed Road Map


Agenda



The Scrum Framework

Who did it already

Proposed Road Map


What is a project?

“ It's a temporary endeavor

undertakento create a unique product, service or

result.” www.pmi.org


Do you experience these?

Planning seems to take too long.

Delivery schedules slip.

You don’t know what to expect from your teams and when.

Estimation is not reliable

Changes are hard to introduce mid-project.


If you have observed one or more of these in your projects, then AGILITY and Scrum can help.


Reasons Why Projects Fail

Over 8000 projects surveyed indicate that the major source of projects failures are:

19%16% 15%

11%10%

9%


What about what is delivered?

Standish Group Survey

When asked about the actual features used.

Most value is in 20% of the delivered solution.

7%

13%

16%

19%

45%

Always Often Sometimes Rarely Never Used


HIGH Uncertainty and Risk


Agenda



The Scrum Framework

Who did it already

Proposed Road Map


• Agility (a.gil.i.ty) -- The ability to rapidly and deliberately respond to changing demand, while controlling risk.

What is Agility?

Agility Speed


Agile methods: https://en.wikipedia.org/wiki/Agile_software_development


2

0

1

6


What is Scrum?An agile framework that relies on inspect and adapt cycles.

Delivers business functionality every 30 days or less.

Founded on empirical process control theory.

A transparent approach for technical and business to have an ongoing conversation.

Easy to understand framework and can be implemented right away.


Takeuchi and Nonaka (1986)-Hitotsubashi University, were researching why some companies were doing better than others in responding to market demand.

Observed a product development model being implemented and called it Scrum.

Japan (日本)

Scrum’s Background


Source: “The New New Product Development Game” by Takeuchi and Nonaka. Harvard Business Review, January 1986.

Rather than doing one thing at a time...

...Scrum teams do a little of everything all the time.

Requirements Design Implementation Test

What they Observed

Project Timeline

Project Timeline


Waterfall and Scrum

Plan Review Execute Manage Change

Traditional planning steps

Pla

n

Exec

ute

Lear

n

Pla

n

Exec

ute

Lear

n

Pla

n

Exe

cute

Lear

n

Pla

n

Exe

cute

Lear

n

Pla

n

Exe

cute

Lear

n

Scrum planning steps

Expect and Embrace Change


Golden Triangle in Agile and Waterfall

Agile estimates Featuresthat can be delivered within time and budget.

Scope

Cost Time

PlanDriven

Scope

ValueDriven

Cost Time

Waterfall estimates Cost and Time for a given set of features.

We Fix

Estimate

WaterfallAgile


Success Rate in Agile and Waterfall


Scrum for Complex Projects

Far from

Certainty

Fa

r fr

om

Ag

ree

me

nt

Close from

CertaintyTECHNLOGYC

los

e f

rom

Ag

ree

me

nt

RE

QU

IRM

EN

TS

Chaotic

Complex

Complicated

Scrum

Simple


Scrum DOES

Enable You to Discover Problems.

Give You Tools to Improve.

Create better working environment.

Let each and every team member knows what they have to do to solve problems.

Alert you when products are in danger of missing their delivery deadlines.


Agenda



The Scrum Framework

Who did it already

Proposed Road Map


•Product owner•Scrum Master•Development Team

Roles

Scrum Framework

•Product backlog•Sprint backlog•Burn Down Chart

Artifacts

•Sprint planning•Daily standup meeting•Sprint review•Sprint retrospective

Events



Meetings


Artifacts


Roles

Scrum Framework


Coach = POReferee = SM

The Players = The team


•Product OwnerRoles

Client Proxy


Servant Leader

•SrumMasterRoles


Problem Solver • The TeamRoles



Roles


Events


Artifacts

Scrum Framework


Release 1

Release 3

Release 2

Decrease Priority

Important => Increase priority

High-priority Items first

Flexible

Interchangeable

Prioritized each sprint

Transparent

Visible

Low Priority Items last

Current Sprint


Prioritized Transparent SizedVisible Flexible


Shows Remaining work

Maintained by the team

Visible


•Product owner•ScrumMaster•Team

Roles

•Product backlog•Sprint backlog•Burndown charts

Artifacts


Events

Scrum Framework


• Sprint PlanningEvents


• Daily Stand UpEvents


• The ReviewEvents


• The RetrospectiveEvents


Role, Artifacts, & Events In Action

Product Owner

Team

RolesProduct OwnerTeamScrum master

ArtifactsProduct BacklogSprint BacklogBurn down chart

EventsSprint PlanningDaily ScrumSprint ReviewRetrospective

The Scrum Team Increment

Scrum Master

Product Backlog

Increment

Sprint


Role, Artifacts, & Events In ActionRolesProduct OwnerTeamScrum master

ArtifactsProduct BacklogSprint BacklogBurn down chart

EventsSprint PlanningDaily ScrumSprint ReviewRetrospective

Increment

Sprint

Daily Scrum

SprintReview

Retrospective

Product Backlog

Sprint Backlog

Sprint Planning Meeting

Product Owner Team

Scrum Master


Agenda



The Scrum Framework

Who did it already

Proposed Road Map


Companies using Agile ScrumBanking Service ProductsSoftware


Scrum Usage by Industry…


Scrum Usage by Company Size…


Agenda



The Scrum Framework

Who did it already

Proposed Road Map


Proposed Roadmap

Our proposed roadmap to implement Scrum is a 3 months plan divided in 3phases in addition to an auditing phase after 6 months:

Consulting Phase: Identify pain points for management and the team (1 week)

Training Phase: Train team members and management to gain tactical agility, scrum skills as well as scrummaster and product owner knowledge. (4 days)

Coaching phase: Transition existing team to scrum (2 months)

Auditing Phase: Revisit the team after having used scrum for a while and audit their adherence to Scrum (1 week)


Agile and Scrum Values

Scrum Values Principles

Iterative ProgressTransparent

Adaption

Inspection

Transparency

Visibility


Things Executives need to do differently

Focus on Value

Accept Hard Truths

Empower Teams

Do LESS at once• Less projects at once• Less complex• Less waste

Adopt new culture that values• Transparency • Collaboration• Continuous improvement


Agile Scrum Essentials

Agile and Scrum History

Waterfall vs. Agile, Agile principles

Scrum Framework

Roles: Scrum Master, Product Owner, Team

Events: Planning, Review, Retrospective, stand up meeting

Artifacts: Product Backlog, Sprint Backlog, Burn down chart.

Backlog creation, Stories, Estimation

Scrum Values

Build a product using scrum

You can retake this course within 12 months for free

Two consecutive days9AM-5PM


Agile Scrum Master

Scrum Framework for SMs.

Simulation building a product.

Heartbeat Retrospectives.

Understanding Team dynamics.

Seeking technical excellence.

Scrum Master cases.

Scaling Scrum Teams.

Agile Engineering practices.

Acceptance Test Driven Development


One Full Day 9AM-5PMPrerequisite Agile Scrum Essential


Agile Product Owner Scrum Framework for POs

Value Driven Development

Product Management

Managing Requirements

Planning Releases

Lean Planning

Managing Products and Releases

Estimating in Scrum

Fixed Cost projects & Scrum

Acceptance Test Driven Development


Two consecutive days9AM-5PM


Keep in touch

THANK YOU!

Joanna El-Khoury

•Email: [email protected]

[email protected]

•Phone: (961) 3 490 314

•LinkedIn: Joannakhoury

•Web: www.scrumarabia.com

mailto:[email protected]

Agile and Scrum for Executives

Business

Transcript of Agile and Scrum for Executives