Final Project Submission: Advanced Scrum Project Management Objective: To expand upon the initial project submitted earlier in the term by applying advanced S

History, Background, and the Manifesto

Modern projects are constrained by several uncertainties

Limitations of Traditional Project Management

1

History, Background, and the Manifesto

handle difficult situations,…….. people

Limitations of Traditional Project Management

2

History, Background, and the Manifesto

It is difficult to change the plan once it is baselined

Limitations of Traditional Project Management

3

History, Background, and the Manifesto

End users see the end product only at the end of the project.

Limitations of Traditional Project Management

4

Traditional Life Cycle

Predictable outcomes arising from up-front plans and specifications, enforced by change management

J. Ross Publishing WAV™ material JR1157- 00_Instructor's Guide 5

PDLC (project Development Life Cycle)

Plan-Driven Lifecycle

Simple and intuitive High ceremony

process, metrics and

documentation

Role of the customer in PD- PDLC ( at arms

length)

however, need to do a lot of

work)

PD-PDLC advantages and disadvantages

JR1157- 00_Instructor'

s Guide J. Ross Publishing WAV™ material 6

build and deliver the specified outcomes according to a master project plan

 Plan-Driven Lifecycle

 Business opportunity

 Simple and intuitive

 High ceremony ( process, metrics and documentation)

 Role of the customer in PD-PDLC ( at arms length, however, need to do a lot of work)

 PD-PDLC advantages and disadvantages

7

Advantage

Fits large and very large projects,

Does not depend on an exceptionally

talented workforce

Lots of tool support

Large, trained base of

practitioners

Intuitively simple to

understand

Rich with reporting, as

usually implemented

 Plan-Driven Lifecycle

 Business opportunity

 Simple and intuitive

 High ceremony ( process, metrics and documentation)

 Role of the customer in PD-PDLC ( at arms length, however, need to do a lot of work)

 PD-PDLC advantages and disadvantages

JR1157- 00_Instructor'

s Guide J. Ross Publishing WAV™ material 8

Disadvantage

Inappropriate where

requirements cannot be fixed,

or where customer changes are

frequent

Inappropriate for small teams, with

fewer than 25 developers

Delivery of business value is

late in the lifecycle

Changes coming late are very expensive to

insert

Heavy, expensive, process and

documentation,

requires governance formality

Agile means getting effective project results

even in complex and uncertain

project requirements,

primarily by

applying small teams—

working collaboratively—

to deliver frequently

increments of business value,

with priority according to

effectiveness, importance, and urgency

9

 Agile Manifesto

 Agile Principles

 Commentary on the 12 Principles

 Other Agile principles

JR1157- 00_Instructor'

s Guide J. Ross Publishing WAV™ material 10

 Agile Manifesto

 Agile Principles

 Commentary on the 12 Principles

 Other Agile principles

JR1157- 00_Instructor'

s Guide J. Ross Publishing WAV™ material 11

Agile Lifecycle

Strategically stable, but tactically emergent, iterative, and incremental

J. Ross Publishing WAV™ material JR1157- 00_Instructor's Guide 20

Agile Lifecycle

Strategically stable, but tactically emergent, iterative, and incremental

J. Ross Publishing WAV™ material JR1157- 00_Instructor's Guide 21

Agile Methodologies

Management simplicity, process discipline, personal safety, and measurable progress

J. Ross Publishing WAV™ material JR1157- 00_Instructor's Guide 22

Agile Methodologies

Management simplicity, process discipline, personal safety, and measurable progress

J. Ross Publishing WAV™ material JR1157- 00_Instructor's Guide 23

Scrum

Team members

Scrum master

Product owner

Product backlog

Scrum

Sprint review

Daily scrum

Sprint backlog

User Story

Product backlog

 Agile Lifecycle

 An Agile manager’s agenda

 Guiding principles for Agile managers

 Addressing the major risks

J. Ross Publishing WAV™ material JR1157- 00_Instructor's Guide 28

 Agile Lifecycle

 An Agile manager’s agenda

 Guiding principles for Agile managers

 Addressing the major risks

JR1157- 00_Instructor'

s Guide J. Ross Publishing WAV™ material 29

• Customers: Coach customers’ and end-users’

• Encourage communications that are open, honest, and real time

• Results: Maintain a focus on results, not specifically on process and activity

• People: Internalize the idea things are managed; people are led

• Champion innovation and technical excellence

An Agile manager’s agenda

 Agile Lifecycle

 An Agile manager’s agenda

 Guiding principles for Agile managers

 Addressing the major risks

JR1157- 00_Instructor'

s Guide J. Ross Publishing WAV™ material 30

• Plans are adaptive.

• Value is the privilege of customers

• Schedule and cost are derived

• Change is embraced and encouraged: • • Documentation comes after personal interaction

• Individuals are trusted

Guiding principles for Agile managers

 Agile Lifecycle

 An Agile manager’s agenda

 Guiding principles for Agile managers

 Addressing the major risks

JR1157- 00_Instructor'

s Guide J. Ross Publishing WAV™ material 31

Addressing the Major Risks Agile methods address the major risks of the traditional methodology that are blamed for poor product quality and poor project performance.

• BDUF: Agile makes no attempt to do a big design up front

• Unknown or unknowable requirements: Customers are allowed to add, delete, revise, and reprioritize requirements at the beginning of each iteration, but not during an iteration.

• Customers at arm’s length: Customers are included s and coached

• Testing and delivery is all at the end of the project cycle

• Documentation is not cost effective: Documentation is minimized …documentation is replaced by daily collaboration and informal means to communicate: e-mail, instant messages, comments em-bedded in the product design, story cards, scorecards, and dashboards.

Module 5 Outline

 Representative Agile Methods

 Methodologies compared

 A process of cycles

 Advantages and Disadvantages of Agile

JR1157- 00_Instructor'

s Guide J. Ross Publishing WAV™ material 32

 Representative Agile Methods

 Methodologies compared

 A process of cycles

 Advantages and Disadvantages of Agile

JR1157- 00_Instructor'

s Guide J. Ross Publishing WAV™ material 33

• Introduction to Agile Project Charters

• Definition and importance of Agile project charters.

### Definition of Agile Methodologies:

• – Agile methodologies involve

iterative and incremental approaches.

• They are characterized by principles like

• flexibility,

• collaboration,

• customer feedback, and

• rapid response to change.

• increasing adoption of Agile methodologies in various industries

### Industries Embracing Agile:

1. **Technology and Software Development:**

• to address the rapidly changing requirements

2. **Marketing and Creative Industries:**

• – to respond quickly to

market trends,

3. **Financial Services and Banking:**

• -for product development

• and to comply with rapidly changing regulations.

4. **Manufacturing:**

• – for product development

5. **Healthcare:**

• – managing complex projects,

Agile Project Charter

• is: “a brief document that

defines the scope,

objectives, and

participants of a project."

• unlike traditional project charters, Agile charters are less about detailed project plans and more about a clear vision and direction.

3. **Importance of Agile Project Charters:**

• "serve as a guiding light for Agile teams

• facilitate flexibility within the defined scope

• help in managing stakeholders'

expectations.

Steps:

1. **Setting Clear but Flexible Goals:**

• – outline the project's goals in a

broad sense.

• – By setting clear objectives without

being overly prescriptive about how to achieve them

**Project Example:** Mobile Health Application Development

• **Clear Goal:** Launch a user-friendly mobile app for fitness and diet tracking on multiple platforms within 6 months.

• **Flexibility:**

• – Development methods and technologies can vary.

• – Features will be delivered incrementally,

• – The team remains open to incorporating new user needs and mew technology

2. **Defining Roles and Responsibilities:**

• – This clarity helps team members

understand their scope of work

• decision-making authority, which is essential for fast-paced Agile environments.

– It allows teams to self- organize and make decisions

quickly

3. **Outlining Scope with Room for Adaptation:**

4. **Establishing Stakeholder Engagement and Expectations:**

5. **Emphasizing Continuous Feedback and Improvement:**

In summary,

• They balance the need for direction and understanding that

change is an inherent part of the project lifecycle,

"What to Include in an Agile Project Charter,"

1. **Project Vision and Mission**: • the purpose, objectives, and expected outcomes

Vision

• The vision is not just a statement; it's the project's heartbeat.

• It encapsulates the purpose—why this project matters, not only to us but to our stakeholders and the community it serves.

• Imagine we’re developing a mobile application

aimed at reducing food waste by connecting local retailers with consumers to sell surplus food at discounted rates.

• The purpose of our project is to combat food waste and promote sustainability.

Objectives

• Objectives are our milestones.

• In the agile world, these are not just static targets; they're dynamic, adaptable, and iterative.

• The objectives might include creating • a user-friendly interface,

• developing a robust notification system, and

• implementing a secure payment gateway by the end of the third quarter.

• These are specific targets that can be broken down into user stories and tasks in our backlog.

• They are the stepping stones that we will reassess and refine in each iteration, always with the end goal in sight.

Expected outcomes

• Expected outcomes are the

tangible changes or benefits we foresee.

• These are the real-world manifestations of our work

• Example

• we are looking to enroll 100 local retailers and achieve 10,000 downloads in the first six months post-launch, thereby reducing food waste by 5%.

**Scope of the Project**:

• the boundaries and limitations of the project are defined.

• It includes what is included and, importantly, what is not included in the project, helping to prevent scope creep.

In Scope • Redesign Of User Interface (Ui)

• Content Update

• Mobile Responsiveness

• User Feedback Implementation

Out Of Scope • 1. Back-End Development

• 2. Rebranding

• 3. E-commerce Integration

• 4. Internationalization

3. **Risks and Issues**:

• identifies potential risks and issues that might arise during the project.

• It includes strategies for mitigating these risks and plans for addressing any issues that occur.

**Example of Risks and Issues:**

• 1. **Risk Identification:**

• – **Technical:** Challenges with new software integration.

• – **Resource:** Availability and skill gaps in the team.

• – **Schedule:** Potential delays due to external dependencies.

• – **Market:** Shifts in market conditions affecting project relevance.

• 2. **Risk Mitigation:**

• – **Technical:** Pilot testing new tools, keeping backup options.

• – **Resource:** Cross-training, maintaining a resource pool.

• – **Schedule:** Adding buffer time, regular vendor communication.

• – **Market:** Regular market trend reviews, stakeholder engagement.

4. **Roles and Responsibilities**:

• This section outlines the roles and responsibilities of each team member.

• It helps in establishing clear

accountability and

ensures that everyone understands their role in the project.

### Example:

• 1. **Product Owner (PO):**

• – **Name:** Alex Johnson

• – **Responsibilities:**

• – Defines project goals and priorities.

• – Manages the product backlog.

• – Acts as the primary liaison between stakeholders and the development team.

• – Ensures the team always works on the most valuable features.

• – Accepts or rejects deliverables.

5. **Stakeholders**:

• Identifying the key stakeholders involved in the project is crucial.

• This includes anyone who has an interest in or is affected by the project’s outcomes.

6. **Success Criteria**:

• Defines how the success of

the project will be measured.

• This could include specific project goals, quality standards, or performance metrics.

7. **Communication

Plan**:

• This part covers how communication will be managed throughout the project.

• It includes methods, frequency, and channels of communication among team members and stakeholders.

8. **Budget and Resources**:

• Details the financial and physical resources available for the project.

• It includes the budget allocation and any constraints or limitations regarding resources.

9. **Timeline and Milestones**:

• Outlines the project timeline, including key milestones and deadlines.

• This helps in tracking progress and ensuring the project stays on schedule

Agile Scope and Requirements

1

Agile scope

2

Evolving, emerging, and adapting Scope as a best value

Agile Scope

u The most important point is that the evolving and emerging scope is managed

J. Ross Publishing WAV™ material JR1157- 00_Instructor's Guide 3

Agile Scope The planning is organized this way

4

The business case holds the product vision in a top-level framework,

Scope is planned incrementally with evolution allowed and encouraged

Planning occurs in shorter frameworks called rolling waves

Development cycles—called iterations or sprints

Agile Scope (A-B-C)

A- Evolving, Emerging, and Adaptive

5

Scope

Schedule

Budget

Quality

Four Levers

Agile Scope

A-1 Best Value

6

customer satisfaction Vs Plan variance

scope is the most flexible

Agile Scope A-1 Best Value

uThe most scope possible— for the available resources—

Agile Scope A-2 Defined

u Scope is

u all the things we must do,

u all the things we want to do,

u all the things we actually do

8

Agile Scope A-3 Backlog

9

• is the scope parsed into • work units, • stories, • use cases, • Tasks

Agile Scope A-4 Architecture

10

• is the scope mapped into • form • function