Agile at Work – Driving

Productive Agile Meetings

Takeaway
• How Agile works in a Team and keypoints in Agile team Management
• How to use Agile to drive productive meetings with your team
Keypoints to remember in Agile
• Less Upfront Planning
• Frequent Improvement
•
Daily Standup

• 15 mins
• What I did Yesterday
• What was done Today
• What are the problems I’m facing
 Sprint Planning
• 4 hrs
• Product Owner gives User
Stories
• Developers Divide stories into
Task, one each day
•
Refining
• Can happen in
Between
sprints
•
Product Review
• 2 hrs
• Review and Demo of work done at end of Sprint
•
Self Improvement
• 2 hrs
• Just after Product Review
•
Conclusion
To drive an Agile Meeting -
• Standup – 15 mins – What I did Yesterday, What was done Today and
What are the problems I’m facing.
• Sprint Planning – 4 hrs – Forecast 2 weeks Plan and divide it into Tasks
• Refining – Meetings to estimate new items in Product Backlog
• Product Review – 2 hrs – At end of Sprint
•
Agile at Work – Planning
with Agile Stories

Presented By - Vikas
Takeaways –
• How to estimate timeline for a sprint using Stories
•
Understanding Agile Story
• 3 Steps –
• Less upfront planning and only predicting a rough plan and deadline for the
project to start with.
• Working on the product on basis of user stories and deliver something each
sprint.
•
Estimating Agile Project
• Define user roles in the Project on basis of the user experience required.
• Generating a story – As a <user role>, I <want/need/can/etc> <goal> so
that <reason>. – Gives Customer’s Language and shows value of the story.
• To write a story keep track of these functions –
• I - Independent
• N - Negotiable
• V - Value
• E - Estimate
• S - Small
• T - Testable
Planning Agile Project
• Charter should be 1 Page with – Vision, Mission & Success
• Use Relative Estimating on stories and tasks
• Use Poker method with stories to assign value to each story
individually to combat group thinking.
• Agile Projects should run like Marathon – Calculating Team Velocity
and then assigning certain numbers of stories at Sprints.
• Developers pick user stories and write tasks to complete it.
•
Conclusion
To be able to Plan Agile Projects -
• Understand Agile Way – Less Upfront, User Stories, Build over time
• Estimating Agile Project – Roles, Story Writing using INVEST
•