Agile world -

Product vision to

continuous delivery

planning

(Scrum framework)

Author :- Sumit Sinha – Senior Business Consultant

CSM (Certified Scrum Master®)

https://ie.linkedin.com/in/sumit-sinha-csm®-epgbm-iim-calcutta-78aaa519

Waterfall vs. Agile

Source: Jim Highsmith

Work to maximize the value delivered in the shortest timeframe possible

Waterfall – Requirements are more Fixed – Resources and Time are more Variable

Agile – Resource and Time are more Fixed – Features are more Variable

Product Vision

Product Roadmap

High Level Release Plan

Sprint Plan

Agile Approach to Planning…

Agile Takes an Iterative

Approach to Planning

Strategic turns Tactical

Vision to execution

Time period shortens

Years to days

Daily

Plan

We plan as much as we have visibility into

We plan continuously throughout the release

Backlog to Delivery….

Functionality of Agile, Scrum

Scrum Framework – Roles, Ceremonies & Artifacts

Scrum Framework

•Sprint planning

•Sprint review

•Sprint retrospective

•Daily scrum meeting

Ceremonies

•Product backlog

•Sprint backlog

•Burndown charts

Artifacts

Sprint backlog…

Do’s….. Involve every team member in the process

Discuss how every item should be

implemented.

Have a definition of done

Identify all kinds of tasks.

Review the sprint commitment.

Evolve the Sprint Backlog during the sprint.

Don’t Don't estimate tasks at all.

Don't assign tasks up front.

Don't use too much time.

The sprint backlog is a simple list of the tasks that must executed by the team

in order to deliver an increment of functional software at the end of that sprint.

Sprint backlog creation happens in the second part of the sprint planning

meeting with the participation of every team member.

“Definition of Done” represent by V - Model

Next Steps

Building a Definition of Done

Backlog - Work Flow