JSA Chapter 06 - Agile Project management.pdf

Agile

1. 05/05/2021
1
Project Management
Agile methodology &
Scrum process
Lecturer: Nguyen Duc Man
Email: [email protected]
Tel: [phone]
Thanks for many of the slides to
Jeff Sutherland
founder of Scrum
Mary Poppendieck
Author of Lean Software
Development
Mike Cohn
Author of Agile Estimation
and Planning
Henrik Kniberg
Crisp, author of Scrum and
XP from the Trenches
Ron Jeffries
XP and TDD founder
Alistair Cockburn
Founder of Crystal
Anders Laestadius
Agile Mgmt coach
Hans Brattberg
XP Coach
Lyssa Adkins
Agile team coach
Overview
Agile way of
working
Alistair Cockburn simplified definition of agile:
Agile is...
Early delivery of business value
With less bureaucracy

2. 05/05/2021
2
Methodology versus Process
❖A methodologyis a box of tools
Use them however/whenever you wish
❖A processis more like an instruction book
The step-by-step kind that come with a new
microwave oven or a TV
❖Agile methodology:
Outlines the types of things that are done but doesn't
specify how to do things
❖Scrum process:
Defines exactly what, when, and/or how various
artifacts are produced
Plan-driven vs. Agile methodology
Plan-driven methodology:
❖It emphasizes formal communications and
control
❖It attempts to be more predictive in nature
Agile methodology:
❖It emphasizes continuous informal
communications and an ability to react to
changes and uncertainty
❖It is more adaptive in nature
Many plan-driven SW projects are like a
cannonball
H
Assumptions:
❖The customer knows what he wants
❖The developers know how to build it
❖Nothing will change along the way
Agile is like a homing missile
Assumptions:
The customer discovers what he wants
The developers discover how to build it
Things 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

3. 05/05/2021
3
Agile
Values & Principles
Agile Manifesto
www.agilemanifesto.org
We are uncovering better ways of developing
software by doing it and helping others do it.
Feb 11-13, 2001
Snowbird ski resort, Utah
Kent Beck
Mike Beedle
Arie van Bennekum
Alistair Cockburn
Ward Cunningham
Martin Fowler
James Grenning
Jim Highsmith
Andrew Hunt
Ron Jeffries
Jon Kern
Brian Marick
Robert C. Martin
Steve Mellor
Ken Schwaber
Jeff Sutherland
Dave Thomas
Agile Manifesto
Individuals and interactionsoverprocesses and tools
Working softwareovercomprehensive documentation
Customer collaborationovercontract negotiation
Responding to changeoverfollowing a plan
That is, while there is value in the items on the right,
we value the items on the left more.
The 4 Values
Principles behind the Agile Manifesto
1 Our highest priority is to satisfy the
customerthrough 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.
5 Build projects around motivated
individuals. Give them the environment and
support they need, and trustthem 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 softwareis 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.
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

4. 05/05/2021
4
Marsmallow
challenge
5 6
Product Owner
movie
“Product Ownership in a nutshell”
Search on YouTube for:
http://www.youtube.com/watch?v=502ILHjX9EE

5. 05/05/2021
5
Agile
Requirements
Scrum process flowchart
Impediment
list
How to create 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
❖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

6. 05/05/2021
6
User Story = User + Story
Save shopping cart
As a buyer
I want to save my shopping
cart
so that I can continue
shopping later
As a <role>,
I want <goal>,
So that <reason>
Independent
Negotiable
Valuable
Estimable
Small
Testable
Acronym courtesy of Bill Wake -www.xp123.com
It is a reminder to have a
conversation with your customer -
not a complete specification
INVEST (User story)
Letter Meaning Description
IIndependent
The user story should be self-contained, in a way
that there is no inherent dependency on another
user story.
N Negotiable
User stories, up until they are part of an iteration,
can always be changed and rewritten.
V Valuable A user story must deliver value to the end user.
E Estimatable
You must always be able to estimate the size of a
user story.
S Scalable (small sized)
User stories should not be so big as to become
impossible to plan/task/prioritize with a certain
level of certainty.
T Testable
The user story or its related description must
provide the necessary information to make test
development possible.
How to handle requirements
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
❖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 capacityfor it in the team
❖Exampel of types of work items in the backlog:
❖Features
❖Bugs
❖Technical work
❖Knowledge acquisition

7. 05/05/2021
7
The product backlog iceberg
In the near future.
Coming weeks/month
In this
Release
In future
Releases
Backlog maintenance
V V
V
Apr
2019
May
2019
June
2019
Q3
2019
Q4
2019
2020
V
2020
2021
2022
2023
Which Backlog is best?
2019
Scrum -
overview
4 pillars of Scrum
Inspect
&
Adapt
Prioritized
product
backlog
Timeboxed
incremental
delivery
Cross-functional
Self organizing
teams

8. 05/05/2021
8
Scrum in a nutshell
Split your organization
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
Optimize process
Optimize business value
Split time
January
Not
c hec k ed out
8d
Bac k of f ic e
LoginI m p l GUI
I n t e g r.
wi t h
J Bo s s
c hec k ed out Done! : o)
DAO
I n t e g r
t e s t
2d1d
GUI W ri t e
s p e c f a i l i n g
2d t e s t
2d
W ri t e
f a i l i n g
t e s t
April
SPRINT GOA L: Beta-r eady r eleas e!
Bur ndow n
Unplanned itemsNex t
W it hdraw
Cl a ri f y
re q u i re-
m e n t s
W ri t e Sa l e s s u p p o rt
f a i l i n g W ri t e
t e s t f a i l i n gt e s t 3d
I m p l
GUI
Scrum process flowchart
Impediment
list
Agile: Scrum definition
❖Scrum is an iterative and incremental agile
software development framework for
managing product development
Definitions:
❖Iterative= Making repetitions
❖Increment= one of a series of
increases (adding)
❖Put them together

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

10. 05/05/2021
10
Sequential vs. overlapping development
Source: “The New New Product Development Game”by Takeuchi and
Nonaka. Harvard Business Review,January 1986.
Rather than doing all of
one thing at a time...
...Scrum teams do a little
of everything all the time
RequirementsDesign Code Test
Scrum framework
•Product owner
•ScrumMaster
•Team
Roles
•Sprint planning
•Daily scrum meeting
•Sprint review
•Sprint retrospective
Ceremonies
•Product backlog
•Sprint backlog
•Burndown charts
•Impediment backlog
Artifacts
Scrum process flowchart
Roles: Red
Ceremonies (meetings): Blue
Artifacts: Green
Impediment
list
Scrum framework
•Sprint planning
•Daily scrum meeting
•Sprint review
•Sprint retrospective
Ceremonies
•Product backlog
•Sprint backlog
•Burndown charts
•Impediment backlog
Artifacts
•Product owner
•ScrumMaster
•Team
Roles

11. 05/05/2021
11
Product owner (Sponsor)
❖Define the features of the product
❖Decide on release date and content
❖Beresponsible for the profitability of the
product (ROI)
❖Prioritize features according to market value
❖Adjustfeatures and priority every iteration, as
needed
❖Accept or reject work results
The Scrum Master
❖Responsible for enacting Scrum values and
practices by facilitating the Scrum process
❖Managing the Impediments backlog
❖Removing impediments
❖Ensure that the team is fully functional and
productive
❖Enable close cooperation across all roles and
functions
❖Shield the team from external interferences
The team
❖Typically 3-8 people
❖Cross-functional:
❖Programmers, testers, user experience designers,
etc.
❖Members should be full-time
❖May be exceptions (e.g., database administrator)
❖Teams are self-organizing
❖Ideally, no titles but rarely a possibility
❖Membership should change only between
sprints
(preferably only between projects…)
What does an agile project manager do?
Work as a Product Owner
or as Scrum Master
or help out in an product owner team
I.e. does not assign work to individuals, but rather
builds the backlog and measures velocity and make
planning from this and the estimates from the team
Reporting and interface to mgmt.
or as a Project Manager but following
agile principles;

12. 05/05/2021
12
Scrum framework
•Product owner
•ScrumMaster
•Team
Roles
•Product backlog
•Sprint backlog
•Burndown charts
•Impediment backlog
Artifacts
•Sprint planning
•Daily scrum meeting
•Sprint review
•Sprint retrospective
Ceremonies
Scrum process flowchart: Ceremonies
Impediment
list
Sprint planning (Before the sprint)
❖Team selects items from the product
backlog they can commit to completing
❖Sprint backlog is created
❖Tasks are identified and each is estimated (1-16
hours)
❖Collaboratively, not done alone by the
ScrumMaster
❖High-level design is considered
Sprint planning meeting
Sprint prioritization
•Analyze and evaluate product
backlog
•Select sprint goal
Sprint planning
•Decide how to achieve sprint goal
(design)
•Create sprint backlog (tasks) from
product backlog items (user
stories / features)
•Estimate sprint backlog in hours
Sprint
goal
Sprint
backlog
Business
conditions
Team
capacity
Product
backlog
Tech-
nology
Current
product

13. 05/05/2021
13
Product & Sprint Backlog Product & Sprint Backlog
As a vacation
planner, I want to
see photos of the
hotels.
Code the middle tier (8 hours)
Code the user interface (4)
Write test fixtures (4)
Code the foo class (6)
Update performance tests (4)
Scrum process flowchart: The Daily Scrum
Impediment
list
The daily scrum
❖Parameters
❖Daily
❖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

14. 05/05/2021
14
Everyone answers 3 questions
❖These are notstatus for the ScrumMaster
❖They are commitments in front of peers
What did you do yesterday?
1
What will you do today?
2
Is anything in your way?
3
The sprint review (After the sprint)
❖Team presents what it accomplished during
the sprint
❖Typically takes the form of a demo of new
features or underlying architecture
❖Informal
❖2-hour prep time rule
❖No slides
❖Whole team participates
❖Invite the world
Scrum framework
•Product owner
•ScrumMaster
•Team
Roles
•Sprint planning
•Daily scrum meeting
•Sprint review
•Sprint retrospective
Ceremonies
•Product backlog
•Sprint backlog
•Burndown charts
•Impediment backlog
Artifacts
Scrum process flowchart: Artifacts
Impediment
list

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

16. 05/05/2021
16
Remaining work (Hours)
40
30
20
10
0
Mon Tue Wed Thu Fri
Tasks
Code the user interface
Code the middle tier
Test the middle tier
Write online help
Mon
14
16
8
12
TuesWedThurFri
8
10
12
50
4
12
12
Done
Done
7
11
Done
8
A sprint burndown chart
Exercise
Daily scrum meeting
Follow up on Burndown chart
(3 volunteers)
Scrum framework
•Product owner
•ScrumMaster
•Team
Roles
•Sprint planning
•Daily scrum meeting
•Sprint review
•Sprint retrospective
Ceremonies
•Product backlog
•Sprint backlog
•Burndown charts
•Impediment backlog
Artifacts

17. 05/05/2021
17
Impediment backlog
❖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
Impediments
Sprint -
Retrospective
3 roles
•Product owner
•Scrum master
Sprint retrospective
Part 1: What happened?
Week 1 Week 2 Week 3
First story
ready for
•Team
3 artifacts
•Product backlog
•Sprint backlog
•Sprint burndown
3 activities
•Sprint planning
•Daily scrum
•Sprint review
•Demo
•Retrospectiv
e
test
New desks
installed
Jeff sick
Story #25
removed
from sprint
Big LAN
argument shootout
Sprint
Team flow! demo

18. 05/05/2021
18
3 roles
•Product owner
•Scrum master
Sprint retrospective
Part 2: How was the energy?
Week 1 Week 2 Week 3
First story
ready for
•Team
3 artifacts
•Product backlog
•Sprint backlog
•Sprint burndown
3 activities
•Sprint planning
•Daily scrum
•Sprint review
•Demo
•Retrospectiv
e
test
New desks
installed
Jeff sick
Story #25
removed
from sprint
Big LAN
argument shootout
Sprint
Team flow! demo
3 roles
•Product owner
•Scrum master
•Team
3 artifacts
•Product backlog
•Sprint backlog
•Sprint burndown
3 activities
•Sprint planning
•Daily scrum
•Sprint review
•Demo
•Retrospectiv
e
Sprint retrospective
Part 3: What do we do differently next sprint?
3 roles
•Product owner
•Scrum masterSprint retrospective
•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
Sprint
Effective velocity over time
(with retrospectives)
7 8 9 10111213
Effective velocity over time
(without retrospectives)
Some highlights from
previous lecture

19. 05/05/2021
19
Project Management
Agile methodology &
Scrum process
Lecturer: Jan Samuelsson
Email: [email protected]
Alistair Cockburn simplified definition of agile:
Agile is...
Early delivery of business value
With less bureaucracy
Scrum process flowchart: Ceremonies
Impediment
list
Product & Sprint Backlog

20. 05/05/2021
20
Product & Sprint Backlog
As a vacation
planner, I want to
see photos of the
hotels.
Code the middle tier (8 hours)
Code the user interface (4)
Write test fixtures (4)
Code the foo class (6)
Update performance tests (4)
Everyone answers 3 questions
❖These are notstatus for the ScrumMaster
❖They are commitments in front of peers
What did you do yesterday?
1
What will you do today?
2
Is anything in your way?
3
Scrum process flowchart: Artifacts
Impediment
list
Remaining work (Hours)
40
30
20
10
0
Mon Tue Wed Thu Fri
Tasks
Code the user interface
Code the middle tier
Test the middle tier
Write online help
Mon
14
16
8
12
TuesWedThurFri
8
10
12
50
4
12
12
Done
Done
7
11
Done
8

21. 05/05/2021
21
A sprint burndown chart
3 roles
•Product owner
•Scrum masterSprint retrospective
•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
Sprint
Effective velocity over time
(with retrospectives)
7 8 9 10111213
Effective velocity over time
(without retrospectives)
Today’s lecture
Scrum -Overview
Summary

22. 05/05/2021
22
Scrum process flowchart
Impediment
list
Scrum is two processes in one
What’s get build
PO and Team together
Product Backlog
Feedback during
Demo/Review
How to work better
Scrum Master, Team and
Product Owner together
Impediments backlog
Feedback during
Retrospective
Scrum!
It’s like playing chess:
A few simple rules
But hard to master

23. 05/05/2021
23
Sprint planning meeting
Sprint progress board
Retrospective meeting
My old company

24. 05/05/2021
24
ESTIMATING
Effort in estimation
100% accuracy is
impossible
Accuracy
100%
For 10% effort you
get 50% easy
You can put too
much effort
This is an
optimistic curve
50%
Effort
10%
Agile risk-management;
Spike, Research, Tracer bullet
Spike
a quick and dirty implementation, designed to be thrown
away, to gain knowledge
indicator: unable to estimate a user story effectively
Research
broad, foundational knowledge-gaining to decide what to
spike or give the ability to estimate
indicator: don’t know a potential solution
Tracer Bullet
very narrow implementation in production quality of an
epic/large user story
indicator: user story is too large in estimation
Agile estimating strategy
❖Estimates done by the people who are going
to do the work
❖Not by the people who want the work done
❖Don’t estimate time (can be debated…)
❖Estimate relative size of stories
❖Easier to come up with
a relative value than an
absolute value
❖Measure velocity per sprint
❖Derive release plan when we
know our velocity
It is twice
as high

25. 05/05/2021
25
Planning poker
http://planningpoker.crisp.se Planning poker app: Scrum Poker Cards (Agile)
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)
Planning Poker
❖Consensus based
❖(we agree on one estimate)
❖Everyone makes an estimate (secret)
❖Forcing people to think independently
❖Avoiding the influence of others
❖Brings together multiple expert opinion
❖Lively dialogue
Planning poker app
Download
❖Planning poker app: Scrum Poker Cards
(Agile)

26. 05/05/2021
26
Planning Poker Exercise -10 min
Relative this Breakfast, how “big” is this Dinner?
Relative: In time it takes to cook/prepare it
❖We will talk more about Estimating SW
development and estimation methods
in later lectures
RELEASE
PLANNING
Velocity-based release planning
❖Velocity = Delivery speed
❖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

27. 05/05/2021
27
Velocity-based release planning
Backlog
Velocity-based release planning
Done!
Jan. 31
Velocity-based release planning
Done! Done!
Feb. 28Jan. 31
Velocity-based release planning
Q2 forecast
None of Some of
these these
All of
these
Done! Done! Done!
Mar. 31Feb. 28Jan. 31

28. 05/05/2021
28
Scope
Release planning –
fixed date
•Today is Aug 6
•Sprint length = 2 weeks
•Velocity = 7 -9
70
What will be done
Quality
Time Cost
PO
by December 24
(10 sprints/20 weeks)
90
Summary
Working smart is more important
than working hard
Working hard
Focus on:
•Hours & personal productivity
•Compliance to plan
•Resource utilization
Working smart
Knows:
•Where we are going & why
•Where we are now
•Impediments
Not
checked out
Focus on:
•Velocity & team productivity
8d
Bac kof f ic e
checked out
GU I
spec
2d
2d
W ri te
fai l i ng
test
D one! :o)SPRINT GOAL: Beta-r eady r elease!
Bur ndown
D A O
Integrtest
2d1d
W ri te
fai l i ng
test
•Quality Login
Integr.w i th
JB oss
Impl GU I Unplanned items
W ri te S al es support
Next
Withdr aw
•Customer feedback
C l ari fy
requi re-
ments
fai l i ng
test
Impl
GU I
W ri te
fai l i ng
test 3d
Find your way through continous learning
There is no one perfect solution for all
organisations, there isn’t even a
perfect solution for one
organisation
Principles and mindset
matters most
Reflexive thinking on all
levels
Continous improvments

29. 05/05/2021
29
Perfection is a direction, not a place
The important thing is not your process.
The important thing is
your process to improve your process
Project Management
Homework
Lecturer: Jan Samuelsson
Email: [email protected]
Scrum process flowchart: Exercise/Quiz
Impediment
list
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
to present your homework in front of the class

30. 05/05/2021
30
Project Management
Team project
Lecturer: Jan Samuelsson
Email: [email protected]
Project topics
❖Canteen Food Ordering
and Management
System
❖Online Bakery Shop
System Php
❖Farming Assistant Web
Service Php
❖Car Comparison
System Project Php
❖Online Blood Bank
Project Php
❖Online Health
Shopping Portal With
Product
Recommendation
❖Online Furniture Shop
Project Php
❖Bikes & Scooters
Rental System
❖Secure Online
Auction System
❖Daily Expense
Tracker System Php
https://nevonprojects.com/php-projects-topics-ideas/
Team project
❖You will plan a project for a product
❖You will get a list to choose from
❖Team consists of 3-5 members (no exceptions)
❖You pick your own team
❖During the course you will do the planning step by
step
❖Presentation will be done by the whole team at the
last lecture in the course
❖Use PowerPoint
❖Prepare for presenting it in English
❖Hand in a paper copy of all documents
Project Plan flow
Purpose
Goals
WBS
Network diagram
Activities and MS
Activity list
Time plan
GANTT
Resource
histogram

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