05/05/2021

Thanks for many of the slides to

Project Management Jeff Sutherland Ron Jeffries
founder of Scrum XP and TDD founder
Mary Poppendieck Alistair Cockburn
Author of Lean Software Founder of Crystal
Agile methodology & Development Anders Laestadius
Scrum process Mike Cohn Agile Mgmt coach
Author of Agile Estimation Hans Brattberg
and Planning XP Coach
Henrik Kniberg Lyssa Adkins
Crisp, author of Scrum and
Agile team coach
XP from the Trenches

Lecturer: Nguyen Duc Man

Email: [email protected]
Tel: 0904235945

Alistair Cockburn simplified definition of agile:

Agile is...
Overview Early delivery of business value

Agile way of With less bureaucracy

working

1
 05/05/2021

Methodology versus Process Plan-driven vs. Agile methodology

❖ A methodology is a box of tools Plan-driven methodology:
Use them however/whenever you wish
❖ It emphasizes formal communications and
❖ A process is more like an instruction book control
The step-by-step kind that come with a new
microwave oven or a TV ❖ It attempts to be more predictive in nature

❖ Agile methodology: Agile methodology:

Outlines the types of things that are done but doesn't ❖ It emphasizes continuous informal
specify how to do things
communications and an ability to react to
❖ Scrum process: changes and uncertainty
Defines exactly what, when, and/or how various ❖ It is more adaptive in nature
artifacts are produced

Many plan-driven SW projects are like a

cannonball Agile is like a homing missile
Assumptions:
Assumptions: The customer discovers what he wants
❖ The customer knows what he wants The developers discover how to build it
❖ The developers know how to build it Things change along the way
❖ Nothing will change along the way
Principle #2:
Welcome changing requirements, even late in
development. Agile processes harness change
for the customer's competitive advantage.

Embrace
Change!

Kent Beck Req Design Code Test

2
 05/05/2021

Agile Manifesto
www.agilemanifesto.org
We are uncovering better ways of developing
software by doing it and helping others do it.

Agile
Feb 11-13, 2001
Snowbird ski resort, Utah

Kent Beck Ron Jeffries

Values & Principles

Mike Beedle Jon Kern
Arie van Bennekum Brian Marick
Alistair Cockburn Robert C. Martin
Ward Cunningham Steve Mellor
Martin Fowler Ken Schwaber
James Grenning Jeff Sutherland
Jim Highsmith Dave Thomas
Andrew Hunt

Agile Manifesto Principles behind the Agile Manifesto

1 Our highest priority is to satisfy the 7 Working software is the primary
The 4 Values customer through early and continuous measure of progress.
delivery of valuable software. 8 Agile processes promote sustainable
2 Welcome changing requirements, even late development. The sponsors, developers,
in development. Agile processes harness and users should be able to maintain a
Individuals and interactions over processes and tools change for the customer's competitive constant pace indefinitely.
advantage 9 Continuous attention to technical
3 Deliver working software frequently, from excellence and good design enhances
a couple of weeks to a couple of months, agility.
Working software over comprehensive documentation with a preference to the shorter timescale. 10 Simplicity--the art of maximizing the
4 Business people and developers must work amount of work not done--is essential.
together daily throughout the project. 11 The best architectures, requirements,
Customer collaboration over contract negotiation 5 Build projects around motivated and designs emerge from self-organizing
individuals. Give them the environment and teams.
support they need, and trust them to get 12 At regular intervals, the team reflects on
the job done.
Responding to change over following a plan how to become more effective, then tunes
6 The most efficient and effective method of and adjusts its behavior accordingly
conveying information to and within a
development team is face-to-face
conversation.
That is, while there is value in the items on the right,
we value the items on the left more.

3
 05/05/2021

Marsmallow
challenge

5 6

Search on YouTube for:

“Product Ownership in a nutshell”

Product Owner
movie

http://www.youtube.com/watch?v=502ILHjX9EE

4
 05/05/2021

Scrum process flowchart

Agile
Impediment
list

Requirements

Terms
❖ User story:
❖A User story capture a description of a feature from an
end-user perspective. It is self-contained and the smallest
unit of work. It is agreed upon by the developers and the
stakeholders
How to create requirements
❖ Epic:
❖Made up of multiple User stories.
May be completed independently, but their business value
isn't realized until the entire epic is complete

❖ Theme:
❖Groups of related stories, usually contributing to a
common goal.
A User story in a Theme can be delivered separately

5
 05/05/2021

User Story = User + Story

INVEST (User story)
Save shopping cart Independent Letter Meaning Description

Negotiable The user story should be self-contained, in a way

As a buyer I Independent that there is no inherent dependency on another
I want to save my shopping
Valuable user story.
cart Estimable User stories, up until they are part of an iteration,
N Negotiable
so that I can continue Small can always be changed and rewritten.
shopping later Testable V Valuable A user story must deliver value to the end user.
Acronym courtesy of Bill Wake - www.xp123.com
You must always be able to estimate the size of a
E Estimatable
user story.
User stories should not be so big as to become
S Scalable (small sized) impossible to plan/task/prioritize with a certain
level of certainty.
As a <role>, It is a reminder to have a
conversation with your customer - The user story or its related description must
I want <goal>, T Testable provide the necessary information to make test
not a complete specification
So that <reason> development possible.

Product backlog (To-do list)

❖ The Product backlog is owned by the
Customer/Product owner

❖ The Product backlog is a prioritized list of work items

How to handle requirements ❖The prioritization makes it possible for the team to know
what is most important to work with

❖ The development team pulls work from the product

backlog as there is capacity for it in the team

❖ Exampel of types of work items in the backlog:

❖Features
❖Bugs
❖Technical work
❖Knowledge acquisition

6
 05/05/2021

Backlog maintenance
V

The product backlog iceberg 2019

V V V
In the near future. 2020
Coming weeks/month Apr
2019
May
2019
June
2019 2021
In this
Q3
Release 2019

Q4 2022
2019

In future
2020
Releases
2023

Which Backlog is best?

4 pillars of Scrum

Scrum - Prioritized
product
Timeboxed
incremental
Inspect
&
Cross-functional
Self organizing

overview
backlog delivery Adapt teams

7
 05/05/2021

Split your organization

Scrum in a nutshell Scrum process flowchart
Split your product

Not Scrum: Large group spending a long time building a huge thing
Scrum: Small team spending a little time building a small thing
... but integrating regularly to see the whole Impediment
list
Optimize process
Optimize business value

Split time
January April

Not
checked out
checked out Done! :o)
SPRINT GOAL: Beta-ready release!

Burndow n
DAO
In te g r
te s t

2d 1d

GUI Wri te
s pec fa i l i n g

2d te s t

2d

8d

Backoffice Wri te
fa i l i n g
te s t
Login Im p l GUI
Unplanned items Next
In te g r.
wi th

J Bo s s

Wri te Sa l e s s u p p o rt
Withdraw
fa i l i n g Wri te

te s t fa ite
lin
sgt 3d

Cl a ri fy
Im p l
re q u i re - GUI
m e n ts

Agile: Scrum definition Definitions:

❖ Scrum is an iterative and incremental agile ❖ Iterative = Making repetitions
software development framework for
managing product development ❖ Increment = one of a series of
increases (adding)

❖ Put them together

8
 05/05/2021

Incremental and Iterative Delivery

Agile: Scrum definition Sprints

❖ Scrum is an iterative and incremental agile ❖ Scrum projects make progress in a series of
software development framework for “sprints”
managing product development ❖Analogous to Extreme Programming iterations
❖ Typical duration is 2–4 weeks
❖ A constant (fixed) duration leads to a better
❖ Scrum divides complex work into simple
rhythm
pieces, large organizations into small teams
❖ Product is designed, coded, and tested
and far-reaching projects into a series of during the sprint
short time horizons called sprints.

9
 05/05/2021

Sequential vs. overlapping development Scrum framework

Roles
•Product owner
Requirements Design Code Test •ScrumMaster
•Team Ceremonies
Rather than doing all of •Sprint planning
one thing at a time... •Daily scrum meeting
...Scrum teams do a little •Sprint review
of everything all the time •Sprint retrospective
Artifacts
•Product backlog
•Sprint backlog
Source: “The New New Product Development Game” by Takeuchi and
•Burndown charts
Nonaka. Harvard Business Review, January 1986.
•Impediment backlog

Scrum process flowchart Scrum framework

Roles
•Product owner
•ScrumMaster
Impediment
list
•Team Ceremonies
•Sprint planning
•Daily scrum meeting
•Sprint review
•Sprint retrospective
Artifacts
•Product backlog
Roles: Red •Sprint backlog
Ceremonies (meetings): Blue •Burndown charts
Artifacts: Green
•Impediment backlog

10
 05/05/2021

Product owner (Sponsor) The Scrum Master

❖ Define the features of the product ❖ Responsible for enacting Scrum values and
❖ Decide on release date and content practices by facilitating the Scrum process
❖ Be responsible for the profitability of the ❖ Managing the Impediments backlog
product (ROI) ❖Removing impediments
❖ Prioritize features according to market value ❖ Ensure that the team is fully functional and
productive
❖ Adjust features and priority every iteration, as
needed ❖ Enable close cooperation across all roles and
functions
❖ Accept or reject work results
❖ Shield the team from external interferences

The team What does an agile project manager do?

Work as a Product Owner

❖ Typically 3-8 people or as Scrum Master
❖ Cross-functional: or help out in an product owner team
❖Programmers, testers, user experience designers,
etc. or as a Project Manager but following
❖ Members should be full-time agile principles;
❖May be exceptions (e.g., database administrator) I.e. does not assign work to individuals, but rather
❖ Teams are self-organizing builds the backlog and measures velocity and make
planning from this and the estimates from the team
❖Ideally, no titles but rarely a possibility Reporting and interface to mgmt.
❖ Membership should change only between
sprints
(preferably only between projects…)

11
 05/05/2021

Scrum framework Scrum process flowchart: Ceremonies

Roles
•Product owner
•ScrumMaster
•Team Impediment
Ceremonies list

•Sprint planning
•Daily scrum meeting
•Sprint review
•Sprint retrospective
Artifacts
•Product backlog
•Sprint backlog
•Burndown charts
•Impediment backlog

Sprint planning (Before the sprint)

❖ Team selects items from the product
Sprint planning meeting
backlog they can commit to completing Team
capacity
Sprint prioritization

❖ Sprint backlog is created Product • Analyze and evaluate product Sprint

backlog backlog goal
❖Tasks are identified and each is estimated (1-16 • Select sprint goal
hours) Business
❖Collaboratively, not done alone by the conditions Sprint planning
ScrumMaster • Decide how to achieve sprint goal
Current (design) Sprint
product • Create sprint backlog (tasks) from
backlog
❖ High-level design is considered product backlog items (user
stories / features)
Tech- • Estimate sprint backlog in hours
nology

12
 05/05/2021

Product & Sprint Backlog Product & Sprint Backlog

As a vacation Code the middle tier (8 hours)

planner, I want to Code the user interface (4)
see photos of the Write test fixtures (4)
hotels. Code the foo class (6)
Update performance tests (4)

Scrum process flowchart: The Daily Scrum The daily scrum

❖ Parameters
❖Daily
Impediment
list ❖15-minutes
❖Stand-up
❖ Not for problem solving
❖Whole world is invited
❖Only team members, ScrumMaster, product
owner, can talk
❖ Helps avoid other unnecessary meetings

13
 05/05/2021

Everyone answers 3 questions The sprint review (After the sprint)

1 ❖ Team presents what it accomplished during

What did you do yesterday? the sprint
❖ Typically takes the form of a demo of new
2 features or underlying architecture
What will you do today? ❖ Informal
❖2-hour prep time rule
3 ❖No slides
Is anything in your way? ❖ Whole team participates
❖ Invite the world
❖ These are not status for the ScrumMaster
❖They are commitments in front of peers

Scrum framework Scrum process flowchart: Artifacts

Roles
•Product owner
•ScrumMaster
•Team Ceremonies
Impediment
list

•Sprint planning
•Daily scrum meeting
•Sprint review
•Sprint retrospective
Artifacts
•Product backlog
•Sprint backlog
•Burndown charts
•Impediment backlog

14
 05/05/2021

Product backlog A sample product backlog

Backlog item Estimate
❖The requirements
Allow a guest to make a reservation 50
❖A list of all desired work on
the project As a guest, I want to cancel a reservation. 12
❖Ideally expressed such that
each item has value to the As a guest, I want to change the dates of a
10
users or customers of the reservation.
product As a hotel employee, I can run RevPAR
32
❖Prioritized by the product reports (revenue-per-available-room)
owner Improve exception handling 25
❖Reprioritized at the start of ... 125
This is the each sprint
product backlog ... 95

Product & Sprint Backlog Managing the Sprint backlog

❖ Individuals sign up for work of their own

choosing
❖Work is never assigned
❖ Estimated work remaining is updated daily
❖ Any team member can add, delete or change
the sprint backlog
❖ Work for the sprint emerges

15
 05/05/2021

Tasks Mon Tues Wed Thur Fri A sprint burndown chart

Code the user interface 14 4 8 Done

Code the middle tier 16 12 10 7 Done

Test the middle tier 8 12 12 11 8

Write online help
Remaining work (Hours) 12 Done

50
40
30
20
10
0
Mon Tue Wed Thu Fri

Scrum framework
Exercise Roles
•Product owner
•ScrumMaster
•Team Ceremonies
Daily scrum meeting •Sprint planning
•Daily scrum meeting
•Sprint review
Follow up on Burndown chart •Sprint retrospective
Artifacts
•Product backlog
•Sprint backlog
(3 volunteers) •Burndown charts
•Impediment backlog

16
 05/05/2021

Impediment backlog Impediments

❖ The Impediment backlog is a

list of things (impediments)
that can stop or slow down the team’s progress
❖The list is prioritized

❖ The log is managed and worked upon by the

Scrum Master

❖ The collection of items in the log is usually done

during the Daily meeting
❖Remember the question: What is stopping me

3 roles
• Product owner
• Scrum master

Sprint retrospective
• Team

3 artifacts
• Product backlog
• Sprint backlog
• Sprint burndown

Part 1: What happened? 3 activities

• Sprint planning

Sprint -
• Daily scrum
• Sprint review
• Demo
• Retrospectiv
e

Retrospective Week 1

New desks
First story
ready for
test Jeff sick
Week 2

Story #25
removed
from sprint
Week 3

Sprint
installed Big LAN Team flow! demo
argument shootout

17
 05/05/2021

Sprint retrospective 3 roles

• Product owner
• Scrum master
Sprint retrospective
3 roles
• Product owner
• Scrum master

Part 2: How was the energy?

• Team
• Team

3 artifacts
Part 3: What do we do differently next sprint?
3 artifacts
• Product backlog
• Product backlog
• Sprint backlog
• Sprint backlog
• Sprint burndown
• Sprint burndown
3 activities
3 activities • Sprint planning
• Sprint planning
• Daily scrum
• Daily scrum
• Sprint review
• Sprint review
• Demo
• Demo
• Retrospectiv
• Retrospectiv e
e

Week 1 Week 2 Week 3

First story
ready for
test Jeff sick
Story #25
removed
from sprint
New desks Sprint
installed Big LAN Team flow! demo
argument shootout

3 roles

Sprint retrospective • Product owner

• Scrum master
• Team

Long term effect 3 artifacts

• Product backlog
• Sprint backlog
• Sprint burndown

3 activities
• Sprint planning
• Daily scrum
• Sprint review
• Demo
• Retrospectiv
e

1 2 3 4 5 6 7 8 9 10 11 12 13
Sprint
Some highlights from
Effective velocity over time
(with retrospectives)
Effective velocity over time
(without retrospectives)
previous lecture

18
 05/05/2021

Alistair Cockburn simplified definition of agile:

Project Management Agile is...

Early delivery of business value
Agile methodology &
Scrum process With less bureaucracy

Lecturer: Jan Samuelsson

Email: [email protected]

Scrum process flowchart: Ceremonies Product & Sprint Backlog

Impediment
list

19
 05/05/2021

Product & Sprint Backlog Everyone answers 3 questions

1
What did you do yesterday?

2
What will you do today?
As a vacation
3
Code the middle tier (8 hours)
planner, I want to Code the user interface (4)
see photos of the Write test fixtures (4) Is anything in your way?
hotels. Code the foo class (6)
Update performance tests (4)
❖ These are not status for the ScrumMaster
❖They are commitments in front of peers

Scrum process flowchart: Artifacts Tasks Mon Tues Wed Thur Fri
Code the user interface 14 4 8 Done

Code the middle tier 16 12 10 7 Done

Test the middle tier 8 12 12 11 8

Write online help 12 Done
Impediment
list

Remaining work (Hours)

50
40
30
20
10
0
Mon Tue Wed Thu Fri

20
 05/05/2021

3 roles

Sprint retrospective • Product owner

• Scrum master
A sprint burndown chart • Team

Long term effect 3 artifacts

• Product backlog
• Sprint backlog
• Sprint burndown

3 activities
• Sprint planning
• Daily scrum
• Sprint review
• Demo
• Retrospectiv
e

1 2 3 4 5 6 7 8 9 10 11 12 13
Sprint

Effective velocity over time

Effective velocity over time
(with retrospectives) (without retrospectives)

Scrum - Overview
Today’s lecture
Summary

21
 05/05/2021

Scrum process flowchart

Scrum is two processes in one

What’s get build How to work better

PO and Team together Scrum Master, Team and
Impediment Product Backlog Product Owner together
list
Impediments backlog
Feedback during
Feedback during
Demo/Review Retrospective

Scrum!
It’s like playing chess:

A few simple rules

But hard to master

22
 05/05/2021

Sprint planning meeting Sprint progress board

Retrospective meeting My old company

23
 05/05/2021

Effort in estimation

ESTIMATING 100% accuracy is

impossible
Accuracy

100%

For 10% effort you

get 50% easy
You can put too 50%

much effort
This is an
optimistic curve

10% Effort

Agile estimating strategy

Agile risk-management;
Spike, Research, Tracer bullet ❖ Estimates done by the people who are going
Spike to do the work
a quick and dirty implementation, designed to be thrown ❖Not by the people who want the work done
away, to gain knowledge
indicator: unable to estimate a user story effectively
Research
broad, foundational knowledge-gaining to decide what to
❖ Don’t estimate time (can be debated…)
spike or give the ability to estimate ❖Estimate relative size of stories
indicator: don’t know a potential solution ❖Easier to come up with
Tracer Bullet a relative value than an
very narrow implementation in production quality of an absolute value
epic/large user story It is twice
indicator: user story is too large in estimation ❖Measure velocity per sprint as high

❖Derive release plan when we

know our velocity

24
 05/05/2021

Planning poker Planning poker process

❖ Discuss the feature that is to be estimated so
everyone understands
❖ Each participant makes their own estimate by
choosing one card and place in front of them
with the back side up (not showing the card)
❖ All show (turn) their card at the same time
❖ Discuss differences in estimates
❖ Agree on one estimate (consensus)
http://planningpoker.crisp.se Planning poker app: Scrum Poker Cards (Agile)

Planning Poker Planning poker app

❖ Consensus based Download
❖(we agree on one estimate)
❖ Planning poker app: Scrum Poker Cards
❖ Everyone makes an estimate (secret) (Agile)

❖ Forcing people to think independently

❖ Avoiding the influence of others
❖ Brings together multiple expert opinion
❖ Lively dialogue

25
 05/05/2021

Planning Poker Exercise - 10 min

Relative this Breakfast, how “big” is this Dinner?

❖ We will talk more about Estimating SW

development and estimation methods
in later lectures

Relative: In time it takes to cook/prepare it

Velocity-based release planning

RELEASE ❖ Velocity = Delivery speed

PLANNING ❖ Velocity measures how much “functionality” a

team delivers in a sprint
❖How many story points, ideal days, days, hours that
was estimated for the delivered features in one sprint

❖ Based on the Team’s velocity they can estimate

what can be delivered in an upcoming sprint
❖And eventually also in a release

26
 05/05/2021

Velocity-based release planning Velocity-based release planning

Done!
Backlog Jan. 31

Velocity-based release planning Velocity-based release planning

Q2 forecast
Done! Done! Done! Done! Done!
None of Some of All of
Feb. 28 Jan. 31 Mar. 31 Feb. 28 Jan. 31
these these these

27
 05/05/2021

Scope

Release planning – Quality

fixed date Time Cost

• Today is Aug 6
• Velocity = 7 - 9
• Sprint length = 2 weeks 70
What will be done

Summary
PO
by December 24
(10 sprints/20 weeks)
90

Working smart is more important Find your way through continous learning
than working hard
Working hard There is no one perfect solution for all
Focus on: organisations, there isn’t even a
• Hours & personal productivity
• Compliance to plan
perfect solution for one
• Resource utilization organisation

Working smart Principles and mindset

Knows:
matters most
• Where we are going & why
• Where we are now
• Impediments
Not
checked out
checked out
Done! :o) SPRINT GOAL: Beta-ready release!
Reflexive thinking on all
Focus on: levels
Burndown
DAO

test
Integr

2d 1d

• Velocity & team productivity

GUI Write
spec failing
test
2d

2d

• Quality
8d

Backoffice Write
failing
test

Login ImplGUI Unplanned items Next

Integr.
with

• Customer feedback
JBoss

Write
failing Write
Sales support Withdraw
failing
test
test 3d

Continous improvments
Clarify
require- Impl
ments GUI

28
 05/05/2021

Perfection is a direction, not a place

The important thing is not your process.

The important thing is
Project Management
your process to improve your process

Homework

Lecturer: Jan Samuelsson

Email: [email protected]

Scrum process flowchart: Exercise/Quiz Instructions: Homework

❖ Each student has his/her own area to present
❖Blue or Red or Green

❖ For example:
❖Describe the roles, main responsibilities
❖Explain the backlogs
❖What is it used for, how we handle it
❖Meetings (what do we do, purpose)
❖Describe other activities

❖ Write down your information.

❖ Give the paper to me next lecture and be prepared
Impediment to present your homework in front of the class
list

29
 05/05/2021

Project topics
❖ Canteen Food Ordering ❖ Online Health
and Management Shopping Portal With
Project Management System Product
❖ Online Bakery Shop Recommendation
System Php ❖ Online Furniture Shop
Team project ❖ Farming Assistant Web Project Php
Service Php ❖ Bikes & Scooters
❖ Car Comparison Rental System
System Project Php ❖ Secure Online
❖ Online Blood Bank Auction System
Lecturer: Jan Samuelsson Project Php ❖ Daily Expense
Email: [email protected] Tracker System Php
https://nevonprojects.com/php-projects-topics-ideas/

Team project Project Plan flow

❖ You will plan a project for a product
❖You will get a list to choose from

❖ Team consists of 3-5 members (no exceptions) Time plan

GANTT
❖You pick your own team
Purpose
Goals
❖ During the course you will do the planning step by
step
Network diagram Activity list
WBS
Activities and MS
❖ Presentation will be done by the whole team at the
last lecture in the course Resource
histogram
❖ Use PowerPoint
❖ Prepare for presenting it in English

❖ Hand in a paper copy of all documents

30
 05/05/2021

Document content Document template

❖ Background & Purpose ❖ I have created a template for the
❖ Goal Product/Project documentation
❖(S.M.A.R.T. and in one sentence)
❖ Requirement list (prioritized)
❖Plus list of Use cases or User stories ❖ Just one document where you put all your
❖ Work Breakdown Structure (WBS) information
❖ Activity list with estimates
❖ Project schedule
❖ Risk analysis (list of all risks) ❖ “Template Project Plan SPM course for Team
❖ Budget project”
❖ EVM (Waterfall) or Burndown chart (Scrum)

31