Radiant Semiconductor

Project Management Development Program – PMDP

Rakesh Bhagam

9/29/2019
Agile Methodologies

9/29/2019
Content
• Waterfall model
• V-model
• Introduction to Agile Methodology
• Agile Team
• Agile Manifesto
• SCRUM & SCRUMEvents
• Requirements, Estimation & Planning
• Tool Overview

9/29/2019

3 1/16/2017
Introduction to waterfall
Methodology
Waterfall: which Let’s find out more
might be more about waterfall
properly called the Methodology.
“traditional”
approach

9/29/2019

4 1/16/2017
 9/29/2019

5 1/16/2017
Introduction to V Model
Methodology
Visually speaking the V-Model is nothing but
a diagrammatic representation of a systems
or software development life cycle. It
summarizes the main verification and
validation preparation steps to be taken in
conjunction with the actual implementation of
the system or software.

9/29/2019

6 1/16/2017
 9/29/2019

7 1/16/2017
Introduction to Agile
Methodology
There are Let’s find out more
projects which about Agile
run by Methodology.
traditional
approach and
agileapproach…

ProjectManager
9/29/2019

8 1/16/2017
Traditional projects & Change
Request
Why do wehave changerequests?
• End user not clear about endresult
• Assumptions differ
• Lackof clarity within developmentteam
• Market changes
• Customer expectation changes

Agile Standpoint; Keepdesigns flexible & Checkwith customers frequently

9/29/2019

1/16/2017
What isAgile ?
• Agile proponents believe
- Current software development processes are too heavyweight
• Too many things are done that are not directly related to
software product being produced

- Current software development is too rigid

• Difficulty with incomplete or changing requirements
• Short development cycles (Internet applications)

- More active customer involvement needed

• CMM focuses on process

9/29/2019

1/16/2017
Continued
…• Agile methods are considered
– Lightweight
– People-based rather than
Plan-based
• Several agile methods
– No single agile method
– XP most popular
• No single definition
• Agile Manifesto closest to a
definition
– Set of principles
– Developed by Agile Alliance
9/29/2019

1/16/2017
TheAgileManifesto

ToUnderstand
Agile waysof
working, along Let’s find outmore
with mindset about Agile Manifesto.
changes weneed
to understand
basic principles

ProjectManager
9/29/2019

1/16/2017
TheAgile Manifesto (February 11-13, 2001)
We are uncovering better ways of
developing software by doing it and helping
others do it.
Through this work we have come to value:

Individuals and interactions over processes and tools

Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan

While there is value in the items on

the right, we value the items on the left more.
9/29/2019
Waterfall Vs Agile

9/29/2019
Waterfall Vs Agile 2

9/29/2019
Scrum

9/29/2019
ScrumTheory
• Scrum is founded on empirical process control theory, or
empiricism.
• Three pillars uphold every implementation of empirical process
control:
• Transparency
• Inspection
• Adaptation

9/29/2019
 Agile Scrum Process

9/29/2019

1/16/2017
Sprint
• Scrum projects make progress in a series of
“sprints”
– Analogous to XP iterations
• Target duration is one month
– +/- a week or two
• But, a constant duration leads to a better
rhythm
• Product is designed, coded, and tested during
the sprint

9/29/2019

1/16/2017
 Sequential vs. overlapping development
Requirements Design Code Test

Rather than doing all of one

thing at a time...

...Scrum teams do a little of

everything all the time

Source: “ T h e New New Product Development Game” by Takeuchi and Nonaka. Harvard Business Review,
January 1986. 9/29/2019
Scrum framework
Roles
•Product owner
•ScrumMaster
•Team
Ceremonies
•Sprint planning
•Sprint review
•Sprint retrospective
•Daily scrum meeting
Artifacts
•Product backlog
•Sprint backlog
•Burndown charts
9/29/2019
1/16/2017
Scrum framework
Roles
•Product owner
•ScrumMaster
•Team
Ceremonies
•Sprint planning
•Sprint review
•Sprint retrospective
•Daily scrum meeting
Artifacts
•Product backlog
•Sprint backlog
•Burndown charts
9/29/2019
1/16/2017

© KPITTechnologiesLimited
Roles :ProductOwner
• Define the features of the product
• Decide on release date and content
• Be responsible for the profitability of the product
(ROI)
• Prioritize features according to market value
• Adjust features and priority every iteration, as
needed
• Accept or reject work results

9/29/2019

1/16/2017
Roles: ScrumMaster
• Represents management to the project
• Responsible for enacting Scrum values and
practices
• Removes impediments
• Ensure that the team is fully functional and
productive
• Enable close cooperation across all roles and
functions
• Shield the team from external interferences

9/29/2019

1/16/2017
Roles : SCRUMTeams

SCRUMteam
Self organized team is
consists of Dev
keyto the Project
team, Product
Success.
manager & Scrum
Master.

ProjectManager
9/29/2019

1/16/2017
Development Whatever needs
to be delivered
Team
• The Dev Team is responsible for implementing the product
• Dev team size is 6(±3) people. (Bigger projects will have multiple
Dev Teams working in parallel with each other.)
• Self-organizing – Dev Team works together to set a realistic target for
the Sprint, and they do their best to hit that target. They are responsible
for delivering high- quality work at a sustainable pace.
• Cross-functional – Dev Team has all the diverse skills needed to
produce working software in a Sprint. Each person might have one (or
more) of the following skills: architecture, coding, testing,
documentation, etc. 9/29/2019

1/16/2017
• We call all these people “Developers,” regardless of their expertise
Scrum framework
Roles
•Product owner
•ScrumMaster
•Team
Ceremonies
•Sprint planning
•Sprint review
•Sprint retrospective
•Daily scrum meeting
Artifacts
•Product backlog
•Sprint backlog
•Burndown charts
9/29/2019
1/16/2017

© KPITTechnologiesLimited
Sprint Planning
• 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 Scrum Master
• High-level design is considered

9/29/2019

29 1/16/2017 © KPITTechnologiesLimited
Sprint planning meeting
Team
Sprint planning meeting
capacity
Sprint prioritization

Product • Analyze and evaluate product Sprint

backlog backlog goal
• Select sprint goal

Business
conditions Sprint planning
• Decide how to achieve sprint goal
(design)
Current
product
• Create sprint backlog (tasks) from Sprint
backlog
product backlog items (user stories
/ features)
• Estimate sprint backlog in hours
Technology

9/29/2019

30
Partsof Sprint Planning Meeting
• 1st Part:
• Creating Product Backlog
• Determining the Sprint Goal.
• Participants: Product Owner, Scrum Master, Scrum Team
• 2nd Part:
• Participants: Scrum Master, ScrumTeam
• Creating Sprint Backlog

9/29/2019

13/16/2017 © KPITTechnologiesLimited
Daily Scrum Meeting
• Purpose
• Make our progress, plans, and blocks visible to each other
• When: Daily, the Dev Team stands in a circle and reports:
• What have I done since the last Daily Scrum
• What do I plan to do by the next Daily Scrum
• What are my blocks
• 15-minute timebox (@10:00)
• During meeting: everyone listens, no discussion
• After meeting is done: further discussion as needed
• Product Owner can attend, but must not interfere
• Scrum Master makes note of the blocks
• After Daily Scrum, Scrum Master helps remove blocks, and people can meet in
smaller groups to discuss issues
9/29/2019
Everyone answers 3questions

1
What did you do yesterday?

2
What will you do today?

3
Is anything in your way?
•Theseare not status for theScrumMaster
•They are commitments in front of peers
9/29/2019

33
Sprint Review
• Purpose: Inspect and Adapt the Product
• When: Last Friday of the sprint (@13:00)
• The Product Owner, Dev Team, Scrum Master, and
stakeholders get “hands on” with what the Dev Team
has produced in the Sprint
• We inspect the quality, and whether it is “done”
• We inspect whether it truly serves customer needs
• We try to find improvements to make in the future
(Product Owner
adds these on the Product Backlog)
• Get real-world customers or end-users to attend and
give hands-on feedback
9/29/2019

• Invite Product Manager for sprint review ever 2 sprints

Sprint Retrospective
• Purpose: Inspect and Adapt Our Process
• When: Last Friday of the sprint (@15:00)
• Last activity in each Sprint (time boxed to 1 hour x the
number of weeks in the Sprint, 2 hours in our case)
• The Dev Team, Scrum Master, and Product Owner
talk about what they experienced and observed during
the Sprint, both positive and negative Start - Stop - Continue
• They create a detailed plan of action for improving in
the next Sprint
• This is the single most important practice in Scrum.
We do this every Sprint!

9/29/2019
 Sprint Retrospective

Start Stop Continue

Start getting a Stop waiting until Continue the
more detailed the end of the good teamwork
understanding of Sprint to begin and positive
Product Backlog testing attitude
Items during
Sprint Planning Stop making Continue putting
changes to our alittle extra
Start doing more target during the buffer in our plan
communication middle of the for each Sprint
between the Dev Sprint
Teamand Product
Owner during the
Sprint

9/29/2019

36 1/16/2017 © KPITTechnologiesLimited
Scrum framework
Roles
•Product owner
•ScrumMaster
•Team
Ceremonies
•Sprint planning
•Sprint review
•Sprint retrospective
•Daily scrum meeting
Artifacts
•Product backlog
•Sprint backlog
•Burndown charts
9/29/2019
1/16/2017

© KPITTechnologiesLimited
Product • The requirements
backlog • 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 sprint

This is the product

backlog
9/29/2019

38 1/16/2017 © KPITTechnologiesLimited
A sample product
backlog Backlog item Estimate
Allow a guest to make a reservation 3
As a guest, I want to cancel a
5
reservation.
As a guest, I want to change the dates
3
of a reservation.
As a hotel employee, I can run RevPAR
8
reports (revenue-per-available-room)
Improve exception handling 8
... 30
... 50
9/29/2019

© KPITTechnologiesLimited
Writing Product Backlog Items
• Scrum does not specify how to write PBI’s
• However, User Stories are a widely used Agile approach to writing requirements
• User stories are very popular among Scrum Teams, and we will be using user
stories for defining product backlog
• A User Story is a short, plain-language description of a feature, centered on who
needs it and why
• A good product backlog is DEEP
• Detailed Appropriately
• Estimated
• Emergent (regularly refined)
• Prioritized (best bang for your bucks) 9/29/2019
User Stories
• User Stories start big, with only the highest-level detail
• We call these “Epics”
• Over time, the Product Owner and Dev Team slice these Epics into smaller and more
detailed stories, as they get closer to being implemented
• This slicing/detailing happens during Product Backlog Refinement
• Goal is for a User Story to be small enough that 1-2 people could finish in 3-4 days
(“1-2-3-4”)
• Non-functional requirements have to be included as user stories (all the *ilities)

9/29/2019
User StoryExamples

9/29/2019
User Stories
• Every User Story has 3 parts
• The 3 C’s: Card, Conversation, Confirmation

As a user
I want to skip to the next or
previous song in the play list
So that I can quickly skip listening
the currently playing song

9/29/2019

14/316/2017
The 2nd C: Conversation
• The card does not include all the detailed information needed by the Dev Team
– and this is intentional!
• User Stories are designed to force a conversation between the Dev Team and
Product Owner
• We want to make it impossible for the Dev Team to start work on a User Story
until they have had a detailed conversation with the Product Owner
• The conversation begins at the start of the project
• The Dev Team and Product Owner will talk through the entire Product Backlog
of User Stories at the project kickoff
• The conversation continues Sprint-by-Sprint
• In Sprint Planning and also during the Sprint
• We document the conversations in the details of the user stories

9/29/2019
The 3rd C:Confirmation
• During the conversations, the Product Owner and Dev Team identify the
confirmations for each User Story
• These are typically acceptance tests that must be passed
• The Dev Team uses these as a guide to development, and as a way of confirming that
the requirements have been met
☐Verify that the HMI has buttons to skip to
next or previous song
☐Verify that the user is able to skip to the next or
previous song in the play list using the soft keys on
HMI
☐Verify that the user is able to skip to the next or
previous song in the play list using the buttons on
the steering wheel
☐Verify that if the user is on first or last song, the
skip wraps around to last to first son in the playlist
9/29/2019
Sprint • A subset of Product Backlog
backlog Items, which define the work for
a Sprint
• Is created ONLY by Team
members
• Each Item has it’s own status
• Should be updated every day
• No more than 300 tasks in the
list
• If a task requires more than 16 hours, it
should be broken down

• Team can add or subtract items from

the list. Product Owner is not allowed
This is the Sprint to do it
backlog
9/29/2019

46 1/16/2017 © KPITTechnologiesLimited
A sample Sprint
backlog

9/29/2019

47 © KPITTechnologiesLimited
Sprint Burn down Chart
• Depicts the total Sprint Backlog hours remaining per day
• Shows the estimated amount of time to release
• Ideally should burn down to zero to the end of the Sprint
• Actually is not a straight line
• Can bump UP

9/29/2019
Do you know how this is
managed?

9/29/2019

1/16/2017
This is how it works…

9/29/2019

1/16/2017
Definition Of Done

• At the end of each Sprint, the Dev Team aims to have an increment (“chunk”) of
the
product done, according to the Definition of Done
• In other words, an ever-increasing, integrated portion of the product, thoroughly
tested and free of defects
• Often referred to as a Potentially Shippable Increment (but you don’t have to ship
it every Sprint – that comes when the Product Owner says it’s complete enough
to ship)
• Anything not “done” (=not finished, or has defects, or needs improvement) gets put
back to the Product Backlog by the Product Owner and prioritized
9/29/2019

1/16/2017
Incremental & IterativeDelivery
• Agile development model is also a
type of Incremental model.

• Software is developed in incremental, rapid

cycles.
• This results in small incremental releases
with each release building on previous
functionality. Each release is thoroughly
tested to ensure software quality is
maintained.

• It is used for time critical applications.

9/29/2019

1/16/2017
Product Backlog Refinement / Backlog
Grooming
• Dev Team, Product Owner, and Scrum Master take time in each Sprint to look
at the upcoming Product Backlog Items which will be worked on in next 2-3
Sprints

• Take large upcoming Product and split them into smaller slices; ideally, small
enough
that 1-2 people could completely finish them in 3-4 days (“1-2-3-4”)
• Get a more detailed shared understanding of the requirements for the
upcoming Product Backlog Items.

• No fixed format, timing, or timebox

• Start with a 2-hour session for Product Owner, Dev Team, and Scrum Master
halfway
9/29/2019
through the Sprint (Friday) and adapt as necessary
Product Backlog Refinement
• We take Product Backlog Items (=User Stories) that will be worked on in
next 2-3 Sprints

• Dev Team, Product Owner, and Scrum Master work together to split
the bigger items into smaller slices
• Dev Team gets a more detailed understanding

Enable user to view

Browsemusic the songs of the
selected Album
by
Album/Artist Enable user to view
the songs of the
selected Artist
Product
Backlog
• Items should be split small enough that 1-2 people could finish
them in 3-4 days (1-2-3-4)
9/29/2019

1/16/2017
Product Backlog Refinement
Browse
music by
Browse by Artist
Album/Artist Browse
music by
Browse Music on the IVI
Enable a user to browse the music Album
stored on the IVI system. The use should
be able to browse the music by Album,
Genre and Artist. For the selected
Album, Artist or Genre, the system
displays the list of the songs available in Display
vertical list.
list of
Browse by Genres
Genre Filter songs
for the
selected
Genre
9/29/2019

1/16/2017
Agile Methodology Overview
Agile is an iterative
and incremental
Letsunderstand Agile
agile software
Methodology, Events
development
and Artifacts!!
framework for
managing product
development.

ProjectManager
9/29/2019

1/16/2017
Basic Guiding
Principle
We all are doing some work and some deliverables are expected out of it
Deliverable could be a decision, schematic, piece of software, prototype, proof
of concept, marketing material, etc.

Prioritized work, set the scope for next 1-2 weeks, make a detailed plan and
execute it. This can be applied to any work we do, personal or professional

Agile is not a process but a behavioral change, we want every one in the organization
to benefit from this positive behavioral change

9/29/2019

60 1/16/2017
Agile Methodology Highlights
• The Product Owner decides what needs to be produced and owns product
backlog

• The Dev Team is self-organizing – it figures out how to get work done.

• The Dev Team plans its Sprints one at a time, at the start of a Sprint.

• The Dev Team decides how much to target in each Sprint.

• The Dev Team’s target is shared, clear, and does not change in Sprint.

• The Dev Team works towards hitting the target on continuous basis.

9/29/2019
Agile Methodology Highlights
• There is a cross-functional Development Team – it has the diverse set of skills
necessary to produce “done” product in a Sprint.

• Each Sprint is a timebox, and is never extended.

• The Dev Team aims for “done” each Sprint = tested and defect-free.

• There is a “Definition of Done”, that tells us what “done” means.

• At the end of the Sprint, we inspect and adapt product and process.

9/29/2019
 SCRUM EVENTS DURATION PER EVENT

Generally 2Hr/week
Sprint Planning Meeting
On day 1 of sprint

15 Mins/day
Daily Scrum
Preferably at the beginning of the day

Product backlog refinement Max 10% of available capacity

1 Hr/week
Sprint Review
Lastday of sprint

Generally 1Hr/week
Sprint Retrospective
Lastday of sprint, Max 3hrs
9/29/2019

1/16/2017
Deliverables on Agile
Project
Deliverables Getting generated during SCRUM

• Cost & Scope estimates

• Prioritized Product Backlog
• Sprint Backlog
• User stories
• Definition of Done
• Incremental delivery
• Final Delivery

9/29/2019

1/16/2017
Requirements, Estimation &
Costing Agile requirements are logged
in product backlog, detailed
Let me into user stories.. We use T-
know shirt sixing/ planning poker
new for estimation.
skills!!!

ProjectManager
9/29/2019

70 1/16/2017 © KPITTechnologiesLimited
Agile Requirement Gathering & Estimation
There is no traditional requirement document used.

In Agile we adopt following process :

• Requirements are gathered in the form of product backlog.
• Requirements are further detailed using user stories & epics.
• These user stories are prioritized discussing with customer and team.
• The team agrees on story point definition & velocity of delivery. Velocity is teams capacity
to deliver user stories in a sprint.
• For the stories the relative size is defined for the stories which are clear enough to
understand the work, risk, quality and other parameters.
• During sprint planning team picks up the stories which have priority depending upon the
velocity and focuses on out what and how to deliver.

9/29/2019
Planning Poker Game

How much time it will take for an

average person to cover 4km distance
without using any vehicle?

9/29/2019
SCRUM-BAN
Scrumban is an Agile management methodology describing hybrids of Scrum and Kanban and was
originally designed asawayto transition from Scrum toKanban.

Today,Scrumban is amanagement framework that emerges when teams employ Scrum astheir chosen way of
working and use the Kanban Method asalens through which to view, understand and continuously improve
how theywork.

SCRUM 9/29/2019
KANBAN
17/416/2017 © KPITTechnologiesLimited
Scaling Agileteams

If agile team There has to be awayto

size grows manage if agile teams size
more than grows more...
12 people
??

ProjectManager
9/29/2019

1/16/2017
The Planning
Pyramid

High-Level Vision
“A low-cost IVI system supporting multiple
smartphone connectivity”

Themes
(Major Areas of Functionality)
FM Radio, BT Support, Navigation, Smartphone
Connectivity, ..
Epics
(Very Large Features)

Stories
(Features in Smaller Slices)

76
9/29/2019

1/16/2017
Tracking

35

30

25

20
ExpectedVelocity
15 Actual Velocity

10

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

9/29/2019

1/16/2017
TeamsDoD

9/29/2019
SprintRetrospective

9/29/2019
AcceptanceCriteria

9/29/2019
Sprint Burndown Chart

9/29/2019
Task Board

9/29/2019
References
1. https://www.mountaingoatsoftware.com/agile/scrum
2. https://www.scrumalliance.org/

9/29/2019

19/616/2017 © KPITTechnologiesLimited
Questions

9/29/2019