You Exec provides business resources that move your career Share this presentation with

forward. Access our full library of presentations, spreadsheet

models, and business book summaries. We do the work, you take colleagues and friends by
the credit.
using your
Errors & Omissions Liability (E&O): You Exec makes no
guarantee that the statements, analysis, projections, estimates,
graphs, reports, numbers, and any derivatives sourced from this Sharing dashboard
presentation are free of errors and omissions. You Exec assumes
no liability for erroneous outcomes derived from this
presentation.
Make sure you log in first to get
rewarded as your friends join.
Please do not resell this presentation. For a commercial or group
license, please visit Unlimited and schedule a demo.
AGILE PROJECT
MANAGEMENT

Presented by You Exec

 THE AGILE METHOD
Agile project management utilizes the principles and application or Agile software development. Unlike traditional project
management, the agile methodology encourages customer needs and collaboration, minimizes resources, increase flexibility to
bring rapid iterations and faster turnaround times.

Customer centricity Contact negotiation

Flexibility Rigid planning

VS
Working solutions
Agile Traditional Comprehensive documentation

Maximum business value Delayed business value due to

in minimum time longer release cycles

Rapid iterations
 ADVANTAGES OF AGILE

70% 65% 59%

Better management of project and Improved project visibility Better alignment between business
change priorities needs and IT

58% 75% 60%

Improved team morale Increased productivity Faster time-to-market

 AGILE PROJECT MANAGEMENT
PROCESS
AGILE PROJECT MANAGEMENT

START & REQUIREMENTS A FEEDBACK & REQUIREMENTS B FEEDBACK & REQUIREMENTS C

PREWOR
K
• Product vision
• Project definition • Requirement 1 • Requirement 1 • Requirement 1
• Original release plan • Requirement 2 • Requirement 2 • Requirement 2
• Contractual agreements • Requirement 3 • Requirement 3 • Requirement 3
 DETAILED AGILE PROCESS

PRODUCT
BACKLOG RELEASE RELEASE BACKLOG
STAKEHOLDERS
MANAGEMENT PLAN MANAGEMENT

DEVELOPMENT REQUEST

Version 1.0

PRODUCT OWNER
Version 2.0

Collects and filters market requirements PREPARES

from key stakeholders REPORTS

Version 3.0
START
RECEIVE DEVELOP IMPLEMEN TEST &
OF
CYCLE REQUIREMEN SOLUTION T PRESENT TO
TS SOLUTION CUSTOMER

AGILE DEVELOPMENT

2ND ROUND
OF SAME PHASE
NO YES
RELEASE
 AGILE METHOD: SCRUM ELEMENTS

Product backlog Daily scrum meeting

• List of requirements for the new product • Daily 15-minute meeting

• Can be changed and adapted at any time • Information meeting

• Requirements are prioritized and divided into work packages • Everyone always knows what each team member is working
on at the moment

Sprint Sprint backlog

• Current iteration • Splitting the work package into smaller packages
• Implementation of a work package • Allocating them to team members
• Fixed duration (timeboxed) • Documentation of the remaining work for each package
• Results in a functional intermediate result

Sprint review meeting Increment

• The team presents the intermediate result to the Product Owner • Work package that is not modified during the sprint
and stakeholders
• Functional intermediate result (Increment of potentially shippable
• Feedback is integrated into the next sprint functionality)
 AGILE METHODS: SCRUM ROLES

STAKEHOLDE SCRUM PRODUCT

CUSTOMER TEAM
R MASTER OWNER

Pays for product development Ensures both business and customer Organized group(s) with Moderator of the project team, Responsible for ensuring overall
with purchases so that the needs are clearly understood and assigned roles and functions to ensures the rules are observed success, represents the interests of
product can be used later incorporated into the development carry out the development and progress is adhered to. users/ stakeholders
process process
 AGILE METHODS: KANBAN PRACTICES
• Visualization of current process
• Displayed on a Kanban board
• Columns correspond to process steps
• Cards correspond to tasks
VISUALIZE WORKFLOW
• Continuous improvement through regular
meetings
• Daily meetings using Kanban Board
• Timeboxing
FEEDBACK LOOP
• Collective definition of process • Limitation of ongoing work
• Agreed-upon guidelines • Prevents multitasking and constant switching
between different tasks
• Creates a better understanding of the purpose of
Kanban
LIMIT WORK IN
MAKE POLICIES EXPLICIT
PROGRESS
• Seamless “flow” of work • Shared corporate vision
• Smooth, fast and steady throughput • Use of models and methods
on the Kanban board
• Continuous change and improvement
• Bottleneck reduction
• Consensus decision-making on changes
COLLABORATIVE
MANAGE WORKFLOW
IMPROVEMENT
 AGILE METHODS: KANBAN BOARD
BACKLOG ACCEPTED IMPLEMENT TEST DONE

TO DO IN PROGRESS DONE

+ Text
Description + Text
Description + Text
Description + Text
Description + Text
Description + Text
Description + Text
Description + Text
Description

Description
+ Text Description
+ Text Description
+ Text Description
+ Text Description
+ Text Description
+ Text Description
+ Text Description
+ Text

+ Text
Description + Text
Description + Text
Description + Text
Description + + Text
Description + Text
Description +

+ Text
Description + + + Text
Description + + + +

+ + + + + + + +

+ + + + + + + +
Pending 04 Analysis 04 Development 05 Test Board 03 Deploy Task 01

Description Text Description Text Description Text Description Text Description Text Description Text Description Text

Description Text Description Text Description Text Description Text Description Text

Description Text Description Text Description Text

Description Text Description Text

 AGILE ROADMAP Risk Level 1 Risk Level 2 Risk Level 3

YEAR 1 YEAR 2

JAN FEB MAR APR MAY JUNE JULY AUG SEPT OCT NOV DEC JAN FEB MAR APR MAY JUNE JULY AUG SEP

Action Description Text

WORK STREM
1
Description Action Action Text Description

Description Description Text Description Description

WORK STREM
2
Description Description Description

Description Action Action Text Description

WORK STREM
3
Action Description Text
 AGILE ROADMAP CATEGORY 1 CATEGORY 2 CATEGORY 3

NOW

FY 1 FY 2

JAN FEB MAR APR MAY JUNE JULY AUG SEPT OCT NOV DEC JAN FEB MAR APR MAY JUNE JULY AUG

Action Text Description

WORK
STREAM 1
Text Action Action Description Description

Text Text Action

WORK
STREAM 2
Text Action Description

• Split the work package into smaller packages • Collective definition of process
GUIDELINE
• Allocate project requirements to team members • Agreed-upon guidelines
S
• Documentation of the remaining work for each package • Creates a better understanding of the purpose of Kanban
 AGILE RELEASE PLAN

PHASE 01 PHASE 02 PHASE 03

LOOP 0 LOOP 1 LOOP 2 LOOP 3 LOOP 4 LOOP 5 LOOP 6

JAN FEB MAR APR MAY JUNE JULY AUG SEPT OCT NOV DEC JAN FEB

Main Goals Description Description Description Description Description Description Description

Implementation
Text Text Text Text Text
Topic

Dependency Team Description

Text Text
1 Text

Dependency Team
Text Text Text Text
2

Dependency Team
Text Text Text
3