Agile Planning

This video will give you a good view on Agile Release Planning and hope this will help you understand Agile Planning better.

IN the agile planning we have 5 core elements: those are


Vision RoadMap Release iteration Daily

Vision :
The vision describes why the project is being undertaken and what is its desired end state.”
or how your product supports the organization's strategies.
vision to themes to features to User Stories.

RoadMap: a step by step, pictorial represetation of acheiving your goal/vision ,presented on the timelines.
Release Planning:a project at hand, Release will be identified based on what all features Customer wants and how soon.
Since during the roadmap we have high level estimates and therefore we wud know by what time the intended features in the release vision
can be developed and delivered.
Resource plan: scrum team 6 +- 3 people,each be a cross functional self organising developer
i.e. u wud hv architech, designer, BA, deve, tester, admin all in the scrum team. each should handle multiple roles.
Define Scrum ROles and Responsibiltities.
Tool and Templates :
RAID log understanidng the project constraints etc.
Process and Procedures in place.
All required Architectural design doc or UI design docs, BRD, FRD etc.
Environmental and infrastructural requirement
Test data mgmt
configuration mgmt will be handled.

Iteration : repetition or a cycle with repeat itself .. refers a sprint here

Daily:
represent the daily task in the sprint that a team will be performing.
Sprint Calendar:
1. Sprint Planning:
if release is big - Generally happens for the current sprint in the previous sprint,for sprint 1 - it would be in sprint 0 (1-2 days iven for prep before sprint starts)
meeting :PO, Dev team and Customers attend.
Sprint 0::
what to built in the next Sprint
PBI are priorized usually ranking them 1,2,3 : 1 being must have, 2- nice to have, 3 - Won't have
Sprint US are streamlined i.e. related US will be aligned to the sprint.
what goes into which Sprints - high/low priority
Check Estimation on US.
define DoD
Check Acceptance criteria is set by PO - atleast for the next sprint.
Estimation workshop.
explain business needs and Release vision.
Derive Velocity: the rate a which team completes work in a sprint, calculated in terms of Story points.
Release kick off.


Daily StandUp meeting : it is timebox to 15mins : team's focus is only on 3 things :
1) what we did yesterday? 2) what are we doing today 3) whats are the impediments.

JAD : Joint Applcation developemet : querying, clarification for the current sprint if any you can have it here. all design gap you discus and sort it out.

Sprint Refinements:
this meeting happens between PO, dev team or SME.
there are many things that may come up while working.. therefore it becomes essential to refine a sprint,
this includes re-prioritize certain items, defer some, include some. Re-evaluate tasks/items in the Sprint Backlog.
Tasks/US that are greater than 12 hours, needs to be brokendown.
Only PO has the final authority to approve/disprove any decision on Sprint Backlog or product Backlog.


CheckPoint Informal Review : checkpoint regarding development progress...where we are, how it's progressing.
Are we are able to meet out commitments or not for the sprint.
What's stoping us etc.


Product Backlog refinement : you would re-look into the features under development and will prioritized US under it.
team jointly decide what US can be the part of which sprint..


Sprint Demo /Review :
remember by this time all ur development for the current sprint should be complete.
what needs to be improved, waht to stop doing or any new add etc.
PO identifies what all items are 'done' or can be shipped or deployyed.

Code deployment : All the done items are picked and deployed into production.


Sprint Retrospective : its for the team who retrospect in the way of woAgile Planning, Release Plan