Project managements / Agile tips

1. AGILE
methodology
tips
2021.10.09/om@

2. AGILE manifesto
4 values
• Individuals and
interactions over processes
and tools
• Working software over
comprehensive
documentation
• Customer collaboration over
contract negotiation
• Responding to change over
following a plan
Agile
is the umbrella term
for all techniques following
the same specific approach to software
development.

3. AGILE
manifesto
12 principles
• Our highest priority is to satisfy the customer
through early and continuous delivery
of valuable software.
• Welcome changing requirements, even late in
development. Agile processes harness change for
the customer's competitive advantage.
• Deliver working software frequently, from a
couple of weeks to a couple of months, with a
preference to the shorter timescale.
• Business people and developers must work
together daily throughout the project.
• Build projects around motivated individuals.
Give them the environment and support they
need,
and trust them to get the job done.
• The most efficient and effective method of
conveying information to and within a
development
team is face-to-face conversation.
• Working software is the primary measure of
progress.
• Agile processes promote sustainable
development.
The sponsors, developers, and users should be
able
to maintain a constant pace indefinitely.
• Continuous attention to technical excellence
and good design enhances agility.
• Simplicity--the art of maximizing the amount
of work not done--is essential.
• The best architectures, requirements, and
designs
emerge from self-organizing teams.
• At regular intervals, the team reflects on how
to become more effective, then tunes and
adjusts
its behavior accordingly.

4. Let’s start AGILE

5. Build a team
with the Tuckman’s stage of team
development model
L'intelligence collective :
capacités cognitives d'une
communauté résultant des
interactions multiples entre
ses membres.

6. Check the team’s mood
with Niko-Niko calendar
Niko-Niko calendar is a tool that makes visible as for the mood of the team, member's feelings, the motivation, and morale

7. Check quality of time invested by the team
with ROTI (Return On Time Invested)
This is a quick and easy method to gauge whether participants feel that the time they spent in a meeting was worthwhile.
The meeting leader asks everyone to rate the meeting from a 0 to 5, with 0 meaning it was a complete waste of time
and 5 signifying an excellent use of time

8. PDCA
Plan/Do/Check/Act-Adjust
PDCA is an iterative design and
management method used in
business for the control and
continuous improvement of
processes and products. It is also
known as the Deming wheel.
(Wikipedia)

9. Define the needs
With PERSONA
A user persona is a representation
of the goals and behavior of a
hypothesized group of users. In
most cases, personas are
synthesized from data collected
from interviews with users.
They are captured in 1–2-page
descriptions that include behavioral
patterns, goals, skills, attitudes, with
a few fictional personal details to
make the persona a realistic
character. (Wikipedia)
Personas help humanize the users and
get to know them on a more personal
level. They encourage design for real
people who have feelings and emotions
rather than for faceless men.
… Which follow INVEST rules
With USER STORY
User story is an informal, natural
language description of features of a
software system. They are written from
the perspective of an end user or user
of a system,
They facilitate sensemaking and
communication; and may help software
teams document their understanding
of the system and its context.
(Wikipedia)

10. Prioritize
with the MoSCoW method
To deliver the greatest and most immediate business benefits early the requirements must be prioritized.
Developers will initially try to deliver all the Must have, Should have and Could have requirements but
the Should and Could requirements will be the first to be removed if the delivery timescale looks threatened.

11. Monitor the progress
with a KANBAN
Kanban is a lean method to manage and
improve work across human systems.
This approach aims to manage work by
balancing demands with available capacity,
and by improving the handling of system-level
bottlenecks.
Work items are visualized to give participants
a view of progress and process, from start to
finish—usually via a Kanban board. (Wikipedia)

12. Monitor the work
with a Burndown chart
A burn down chart is a graphical
representation of work left to do versus
time.

13. Estimate effort/time
with « Planning Poker»
Planning poker, is a consensus-based, gamified
technique for estimating,
mostly used for timeboxing in Agile principles.
In planning poker, members of the group make
estimates by playing numbered cards face-down
to the table,
instead of speaking them aloud.
The cards are revealed, and the estimates are then
discussed.
By hiding the figures in this way, the group can
avoid the cognitive bias of anchoring,
where the first number spoken aloud sets a
precedent for subsequent estimates. (Wikipedia)

14. Optimize your time
with POMODORO technique
The Pomodoro Technique is a time
management method developed by
Francesco Cirillo in the late 1980s.
It uses a timer to break work into intervals,
traditionally 25 minutes in length, separated
by short breaks. Each interval is known as a
pomodoro, from the Italian word for 'tomato’.
(Wikipedia)

15. Retrospective’s
wheel
A periodic review to see :
- A periodic review to see:
- What to KEPT
- What to ADD or STOP
- What to do LESS or MORE

16. In summary
• MoSCoW method
• KANBAN
• BURDOWN Chart
• PLANNING Poker
• POMODO technique
• Retrospective’s wheel
• TUCKMAN’s stage of team
development
• NIKO NIKO calendar
• ROTI (Return On Time Invested)
• PERSONA
• USER STORY