Search Header Logo
Agile Project Management

Agile Project Management

Assessment

Presentation

Business

12th Grade

Practice Problem

Hard

Created by

Lilly Cuffy

Used 8+ times

FREE Resource

11 Slides • 0 Questions

1

media

AGILE PROJECT
MANAGEMENT

Ms. Cuffy

Business Management and Law

2

media

AGENDA

Introduction: The agile project management

approach

Frameworks: Values and Principles
Primary Goals: Draft an Agile Project Management

Value and Principle based-plan

Areas of Growth: Identify the differences between

Traditional and Agile Project Management

Timeline: End of Second Quarter
Summary: Understand the Traditional Project

Management approach and compare it to Agile
Project Management and then decide what
is the best route to take for the customer.

3

media

INTRODUCTION

Agile Manifesto- isa document that sets out
the key values and principles behind the Agile
philosophy and serves to help development
teams work more efficiently and sustainability.

Agile methodologies- frameworks that teams
and organizations use to put the Agile mindset
into practice.

Source: Msik12.com- Broward County

4

media

FRAMEWORKS

The four Core Values from the Agile Manifesto emphasized
experience over theory,

1.

Interaction with people instead of processes and tools

2.

Using software rather than documentation,

3.

Collaborate with the Customer

4.

Adapting to change rather than following a plan.

Source: Msik12.com- Broward County

5

media

FRAMEWORKS

Scrum is an agile framework composed of principles and values of respect for
people involved, self-organization, and competency to solve complex problems.

It is based on the pillars of transparency, inspection, and adaptation.

It includes a scrum team, roles, events (sprint, sprint planning, daily scrum, sprint
review, sprint retrospective), and artifacts (product backlog, sprint backlog,
increment). It is used by large corporations, small businesses and individuals to
help them reach their goals

Sprint - An abbreviated time interval within a project during which a usable and
potentially releasable increment of the product is created.

Sprint Planning – Lays out the work performed in the sprint.

Daily Scrum – Meetings that occur daily to inspect goals progress and aims.
Adaption of the sprint backlog would take place here if needed.

Sprint Review – Inspects the outcomes of the Sprint to determine future
adaptations usually resulting in a revised Product Backlog.

Sprint Retrospective – Identifies improvements to apply to the next Sprint. A
more formal way to plan and implement changes for future effectiveness and
quality

Source: Msik12.com- Broward County

6

media

PRODUCT BACKLOG – ORDERED LIST OF WHAT IS NEEDED TO IMPROVE A PRODUCT - THE
SOURCE OF WORK THAT THE SCRUM TEAM DOES.

SPRINT BACKLOG – PER SCRUM.ORG, “THE SPRINT BACKLOG IS COMPOSED OF THE SPRINT
GOAL (WHY), THE SET OF PRODUCT BACKLOG ITEMS SELECTED FOR THE SPRINT (WHAT), AS
WELL AS AN ACTIONABLE PLAN FOR DELIVERING THE INCREMENT (HOW). THE SPRINT
BACKLOG IS A PLAN BY AND FOR THE DEVELOPERS. IT IS A HIGHLY VISIBLE, REAL-TIME
PICTURE OF THE WORK THAT THE DEVELOPERS PLAN TO ACCOMPLISH DURING THE SPRINT IN
ORDER TO ACHIEVE THE SPRINT GOAL.”

INCREMENT – THE “STEPPINGSTONE TOWARDS THE PRODUCT GOAL”.
SCRUM IS A PROJECT MANAGEMENT METHODOLOGY THAT USES A TEAM-BASED APPROACH
WITH THREE PRIMARY ROLES:
1.THE SCRUM MASTER - THE SCRUM MASTER IS RESPONSIBLE FOR OWNING THE SCRUM

PROCESS, FACILITATING TEAM MEETINGS, AND RESOLVING ISSUES.
2.THE PRODUCT OWNER - THE PRODUCT OWNER IS RESPONSIBLE FOR MANAGING THE

PRODUCT BACKLOG, WRITING THE VISION STATEMENT AND RELEASE PLANS, AND MANAGING
CUSTOMER AND STAKEHOLDER EXPECTATIONS.
3.DEVELOPMENT TEAM THE DEVELOPMENT TEAM IS RESPONSIBLE FOR DOING THE WORK IN

A SPRINT, MEETING FOR A DAILY SCRUM, AND CREATING A SPRINT BACKLOG.

AT THE END OF THE SPRINT, THE TEAM INVITES STAKEHOLDERS TO A SPRINT REVIEW TO
INSPECT THE PROJECT AND PRODUCT GOALS AND MAKE ANY NECESSARY IMPROVEMENTS
AS A SCRUM PROFESSIONAL, ONE OF THE MOST IMPORTANT TOOLS TO TRACK THE PROGRESS
OF A PROJECT IS THE BURNUP AND BURNDOWN CHART. THIS CHART IS USED TO MEASURE
HOW QUICKLY A TEAM IS PROGRESSING TOWARD THE COMPLETION OF A PROJECT.

SOURCE: MSIK12.COM- BROWARD COUNTY

FRAMEWORKS

7

media

THE WAY TO GET
STARTED IS TO QUIT
TALKING AND BEGIN
DOING.

Walt Disney

8

media

TIMELINE- TO COMPLETE AT END OF 2ND QTR.

To start a presentation, go to the Slide Show
tab, and select From Beginning.

Title

To display Presenter view, in Slide Show
view, on the control bar at the bottom left
select the three dots, and then Show
Presenter View.
Title

During your presentation, the speaker notes
are visible on your monitor, but aren't visible
to the audience.

Title

The Notes pane is a box that appears below
each slide. Tap it to add notes.
Title

If you don’t see the Notes pane or it is
completely minimized, click Notes on the
task bar across the bottom of the
PowerPoint window.

Title

9

media

SUMMARY

SUMMARY

SUMMARY

A burn-up chart is a graphical representation of the

progress that has been made on a project over a given
period of time, while a burndown chart shows how much
work is still to be done in order to finish the project. A
burnup chart is useful for tracking the overall progress
of a project As the project progresses, the burnup chart
will show how many tasks have been completed,
allowing you to gauge the overall progress of the project.

A burndown chart, on the other hand, is used to track
the progress of individual tasks. It shows which tasks
are still to be done. The y-axis typically displays the total
number of tasks, and the x-axis displays the timeline.

Source: msik12.com- Broward County

Students need to know that Kanban is a visual system developed by Japanese
engineer Taiichi Ohno in the 1940s for tracking projects.

It organizes tasks into columns, such as 'To Do', 'In Progress' and 'Completed', and
uses color-coding and swimlanes to further organize information.

It limits work in progress (WiP) to promote efficiency and transparency, with roles
such as the Service Delivery Manager (for downstream flow) and Service Request
Manager (for upstream flow) ensuring that tasks are completed on time and within
budget. Kanban also encourages feedback and continuous improvement so that
teams can explore ideas and solutions.

Kanban is an Agile-based method of tracking progress on projects and tasks.

It involves two sets of principles - Change Management Principles, which focus on
minimizing disruption while maximizing savings, and Service Delivery Principles,
which focus on customer desires, self-organization, and regular reviews. It also
includes metrics like lead time, cycle time, and project throughput, as well as charts
and diagrams, like the CFD, to measure progress.

Source: msik12.com- Broward County

10

media

FINAL SUMMARY

Understand the Traditional project Management approach
and compare it to Agile Project Management and then
decide what is the best route to take for the customer.

11

media

THANK YOU

Ms. Cuffy

Lillia.cuffy@browardschools.com

media

AGILE PROJECT
MANAGEMENT

Ms. Cuffy

Business Management and Law

Show answer

Auto Play

Slide 1 / 11

SLIDE