19/06/1442

Mo Ishag Designs

1 An Introduction To Agile 7
2 Life Cycle Selection 16
3 Creating An Agile Environment 24
4 Charter The Project And The Team 34
5 Organizational Considerations for Project Agility 43
6 Overview Of Agile And Lean Frameworks 54

Contents
2

1
19/06/1442

Preface
• The vision for this practice guide is to

equip project teams with

tools, situational guidelines, and an
understanding of the available agile
techniques and approaches to enable
better results.

The need for agile approach

Common
language
Openness

Flexibility

Multiple ways to achieve

successful delivery (not
just one path of
standard processes)
4

2
19/06/1442

Agile is spreading

• Education is a prime and fertile ground

to expand agile practices
• Teachers in middle schools, high
schools, and universities around the
world are beginning to use agile to
create a culture of learning.

An Introduction
To Agile

1 6

3
19/06/1442

An Introduction to Agile
Definable Work vs. High-uncertainty work
• High-uncertainty projects have high rates of change,
complexity, and risk. These characteristics can present
problems for traditional predictive approaches that aim
to determine the bulk of the requirements upfront and
control changes through a change request process.

Agile approaches were created to explore

feasibility in short cycles and quickly adapt
based on evaluation and
feedback.

The Agile Manifesto and Mindset

• We are uncovering better ways of developing software by
doing it and helping others do it.
Individuals and Processes and
We value interactions over tools

Comprehensive
Working software over documentation
Customer Contract
collaboration over negotiation
Responding to
over Following a plan
change

we value the items on the while there is value in the

left more. items on the right
8

4
19/06/1442

The Twelve Principles Behind

the Agile Manifesto
1. Our highest priority is to satisfy the customer through
early and continuous delivery of valuable software.
2. Welcome changing requirements, even late in
development. Agile processes harness change for the
customer’s competitive advantage.
3. Deliver working software frequently, from a couple of
weeks to a couple of months, with a preference to the
shorter timescale.
4. Business people and developers must work together
daily throughout the project

The Twelve Principles Behind

the Agile Manifesto
5. Build projects around motivated individuals. Give them
the environment and support they need, and trust them
to get the job done.
6. The most efficient and effective method of conveying
information to and within a development team is face-
to-face conversation.
7. Working software is the primary measure of progress.
8. Agile processes promote sustainable development. The
sponsors, developers, and users should be able to
maintain a constant pace indefinitely.

10

5
19/06/1442

The Twelve Principles Behind

the Agile Manifesto
9. Continuous attention to technical excellence and good
design enhances agility.
10. Simplicity—the art of maximizing the amount of work
not done—is essential.
11. The best architectures, requirements, and designs
emerge from self-organizing teams.
12. At regular intervals, the team reflects on how to become
more effective, then tunes and adjusts its behavior
accordingly.

11

The Relationship Between the Agile

Manifesto Values, Principles, and Common
Practices

12

6
19/06/1442

Uncertainty, Risk, and Life Cycle

Selection
• Some projects have considerable uncertainty
around project requirements and how to fulfill
those requirements using current knowledge
and technology. These uncertainties can
contribute to high rates of change and project
complexity. These characteristics are
illustrated in the next slide

13

Uncertainty and Complexity Model Inspired by

the Stacey Complexity Model

14

7
19/06/1442

15

Life Cycle
Selection

2 15

Life Cycle Selection

• Four types of life cycles:

1 Predictive
Iterative 2
3 Incremental
4 Agile
16

8
19/06/1442

Life Cycle Selection

• Four types of life cycles:

1 Predictive life cycle

A more traditional approach, with the bulk of planning
occurring upfront, then executing in a single pass.
sequential process

17

Life Cycle Selection

• Four types of life cycles:

2 Iterative life cycle

An approach that allows feedback for unfinished work to
improve and modify that work

18

9
19/06/1442

Life Cycle Selection

• Four types of life cycles:

3 Incremental life cycle

An approach that provides finished deliverables that the
customer may be able to use immediately.

19

Life Cycle Selection

• Four types of life cycles:

4 Agile life cycle

An approach that is both iterative and incremental to
refine work items and deliver frequently.

20

10
19/06/1442

Characteristics of Project Life

Cycles

21

The Continuum of Life Cycles

22

11
19/06/1442

23

Creating An Agile
Environment

3 23

Start With An Agile Mindset

• Managing a project using an agile

approach requires that the project team
adopt an agile mindset. The answers to
the following questions will help to
develop an implementation strategy:
Agile

24

12
19/06/1442

Start With An Agile Mindset

1 2
How can the project team act
in an agile manner?
What can the team deliver
quickly and obtain early
feedback to benefit the next
delivery cycle?

3 4
What work can be avoided in
How can the team act in a
order to focus on high-priority
transparent manner?
items?

Agile

5
How can a servant-leadership
approach benefit the
achievement of the team’s
goals?

25

Servant Leadership Empowers

The Team

• Agile approaches emphasize servant

leadership as a way to empower
teams.

26

13
19/06/1442

Servant Leadership Empowers

the Team

Servant Leader Responsibilities

• Servant leaders manage relationships
to build communication and
coordination within the team and
across the organization.

27

Servant Leadership Empowers

the Team

• When project managers act as servant

leaders, the emphasis shifts from
“managing coordination” to
“facilitating collaboration.”

28

14
19/06/1442

Servant Leadership
Responsibilities

• Servant leaders can have many possible

titles, but what is most important is
what they do. Here are some examples
of the responsibilities a servant leader
may have:

29

Servant Leadership
Responsibilities
• Education • Help the team with
Educate stakeholders technical project
around why and how to management activities like
be agile. quantitative risk analysis.

• Support • Celebrate
the team through team successes and support
mentoring, and bridge building activities
encouragement, and with external groups.
support.

30

15
19/06/1442

Role Of The Project Manager In

An Agile Environment
• The role of the project manager in an
agile project is somewhat of an
unknown, because many agile
frameworks and approaches do not
address the role of the project manager.

31

Agile Team Roles

In agile, three common roles are used:
Agile Roles

Cross-functional
Product owner Team facilitator
team members

Cross-functional teams The product owner is The third role typically seen
consist of team responsible for guiding on agile teams is of a team
members with all the the direction of the facilitator, a servant leader.
skills necessary to product. Product This role may be called a
produce a working owners rank the work project manager, scrum
product. based on its business master, project team lead,
value. team coach, or team
facilitator.

32

16
19/06/1442

33

Charter The Project

And The Team

4 33

Charter The Project And The

Team

• At a minimum, for an agile project,

the team needs the project vision
or purpose and a clear set of working
agreements.
• An agile project charter answers the
following questions:

34

17
19/06/1442

Charter The Project And The

Team

1 Why are we doing this

project? This is the
project vision.
2 Who benefits and how?
This may be part of the
project vision and/or
project purpose.

3 What does done mean

for the project? These
are the project’s release
4 How are we going to
work together? This
explains the intended
criteria. flow of work.

35

Common Agile Practices

• .

The single most important practice is the

retrospective because it allows the team
to learn about, improve, and adapt its
process.

RETROSPECTIVES Retrospectives help the team

learn from its previous work
on the product and its process

36

18
19/06/1442

Common Agile Practices

• .

The backlog is the ordered

list of all the work,
presented in story form,
for a team.

BACKLOG
PREPARATION

37

Common Agile Practices

• .

In iteration-based agile, the product

owner often works with the
team to prepare some stories for
the upcoming iteration during
one or more sessions in the
BACKLOG middle of the iteration.
REFINEMENT

38

19
19/06/1442

Common Agile Practices

• .

Teams use standups to

microcommit to each other,
uncover problems, and ensure
the work flows smoothly through
the team..

DAILY
STANDUPS Timebox the standup to no longer
than 15 minutes.

39

Common Agile Practices

• .

As the team completes the features

usually in the form of user stories,
the team periodically
demonstrates the working
product.

DEMONSTRATIONS/
REVIEWS The product owner sees the
demonstration and accepts or
declines stories.
40

20
19/06/1442

Common Agile Practices

• .

Teams consider their story size so

they do not try to commit to more
stories than there is team
capacity to complete within one
iteration.
PLANNING
FOR
ITERATION-BASED Each team’s capacity is different.
AGILE Each product owner’s typical
story size is different.
41

42

Organizational
Considerations for

5 Project Agility
42

21
19/06/1442

Procurement and Contracts

• Agile Manifesto values:

Customer over
Contract
collaboration negotiation

• Some contracting techniques that

can formalize this dynamic
include the following:

43

Procurement and Contracts

Rather than formalizing an entire contracting

relationship in a single document, project
parties can achieve more flexibility by
describing different aspects in different
documents.

44

22
19/06/1442

Procurement and Contracts

Many vendor relationships are governed by

fixed milestones or “phase gates” focused
on intermediate artifacts, rather than a
full deliverable of incremental business
value.

45

Procurement and Contracts

Rather than lock an entire project scope and

budget into a single agreement, a project.
can decompose the scope into fixed-price
microdeliverables, such as user stories.

46

23
19/06/1442

Procurement and Contracts

Customers incur unwanted risk from a

traditional time and materials approach.
One alternative is to limit the overall
budget to a fixed amount. This allows the
customer to incorporate new ideas and
innovations into the project not originally
planned. .

47

Procurement and Contracts

Another alternative is a shared financial risk

approach. In agile, the quality criteria are
part of what done means.

48

24
19/06/1442

Procurement and Contracts

When an agile supplier delivers sufficient

value with only half of the scope
completed, the customer should not be
bound to pay the remaining half if the
customer no longer needs it.

49

Procurement and Contracts

For those contracts with a fixed budget, a

supplier may offer the customer the
option to vary the project scope at
specified points in the project.

50

25
19/06/1442

Procurement and Contracts

Arguably the most collaborative

contracting approach is to embed the
supplier’s services directly into the
customer organization.

51

Procurement and Contracts

In order to diversify risk, customers may seek

a multisupplier strategy. However, the
temptation will be to contract the work
such that each supplier does only one
thing, which creates a web of
dependencies before any usable service or
product emerges..

52

26
19/06/1442

53

Overview Of Agile
And Lean

6 Frameworks
53

SCRUM
Scrum is a single-team process framework
used to manage product development.
The framework consists of Scrum roles,
events, artifacts, and rules, and uses an
iterative approach to deliver working
product.

• Scrum is run on timeboxes of 1 month or less with

consistent durations called sprints where a potentially
releasable increment of product is produced.

54

27
19/06/1442

SCRUM The Scrum team consists of

Product Owner Maximizes the value

of the product.

Delivers working Development

product Team
Scrum Master
ensuring the Scrum process is upheld /
coaches the team on removing impediments
55

Scrum Events and Artifacts

56

28
19/06/1442

Extreme Programming

eXtreme Programming (XP) is a software

development method based on frequent
cycles. based on the philosophy of
distilling a given best practice to its
purest, simplest form, and applying that
practice continuously throughout the
project.

57

Kanban Method

Kanban in lean manufacturing is a system

for scheduling inventory control and
replenishment.
The word kanban is literally translated as
“visual sign” or “card.”

58

29
19/06/1442

Defining principles and

properties of Kanban Method

Start with current state Visualize the workflow

Agree to pursue incremental, Limit work in progress

evolutionary change
Manage flow
Respect the current process, roles,
Make process policies explicit
responsibilities, and titles
Implement feedback loops
Encourage acts of leadership at all
levels improve collaboratively

59

Kanban Board

60

30
19/06/1442

SCRUMBAN

Scrumban is an agile approach originally designed

as a way to transition from Scrum to Kanban.
As additional agile frameworks and
methodologies emerged, it became an evolving
hybrid framework in and of itself where teams
use Scrum as a framework and Kanban for
process improvement.

61

SCRUMBAN

In Scrumban, the work is organized into small

“sprints” and leverages the use of kanban
boards to visualize and monitor the work.

62

31
19/06/1442

Scaling Frameworks

Scrum of Scrums (SoS), also known as “meta

Scrum,” is a technique used when two or more
Scrum teams consisting of three to nine
members each need to coordinate their work
instead of one large Scrum team.
.

63

Representatives of Scrum Teams Participating in SoS teams

64

32
19/06/1442

65

66

Questions?
66
Mo Ishag Designs

33