Your SlideShare is downloading. ×
Agile :what i learnt so far
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Agile :what i learnt so far

322

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
322
On Slideshare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
1
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Agile : What I learnt so far @RohanChandane
  • 2. Practices 1. Management Practices 2. Development Practices 3. Testing Practices
  • 3. 1. Management Practices - Inception - Story Estimation & Prioritization - Scrum - IKO - Standup - Retrospective
  • 4.
  • 5. Inception - Product intro - Budget allocation - Wireframes / Screenshots - User journeys - Data flow diagram - Epics creation - Story creation
  • 6. Story Estimation - Poker cards - T Shirt Size
  • 7. Story Prioritization - Prioritization of stories was based on - must have features - good to have features - total project budget allocation - Adding prioritized stories to backlog
  • 8. Scrum - 2 weeks sprint cycle - Picking up the stories for next release - From product backlogs - No of picked stories are based on - Total points allocated for that particular sprint - Developer pair count - Actual deliverable at the end of the sprint
  • 9. IKO - Iteration Kick Off General discussion/ analysis about - What we going to deliver in this sprint - Looking at previous incomplete stories - Picking up new stories for the interaction - Discussing stories in details with dev team
  • 10. ... - Why IKO - Because not all Developers / QAs were involved in inception - IKO to Story Analysis section on board: - Retrospected - General discussion about project was moved to product brief in scrum meeting (BA was responsible for that)
  • 11. Standup - Quick standup (practicing it with fixed time) - 10 min stand up, on time (eg. at 9:10am) - alarm at 9:20am to make it a habit of 10 min stand up - What to achieve from each individual - What I did yesterday - What I am going to do today - What help I may need from team today
  • 12. ... - Intervention techniques - Raising hand - if topic is not related to entire team - so that it can be discussed separately - Daily standup host rotation - Everybody gets an idea about what's going on with all stories
  • 13. Retrospectives - Practice Retro regularly - An hr / week (eg. on friday, in 2nd half of the day) - Helps to resolve issues quickly - Take quick actions on issues in next week - Discuss previous issues in next retro before starting with new retro topics
  • 14. Retrospectives - This can be format for retro board What went wrong What went right What we should keep doing What we should stop doing
  • 15. ... Some other ideas for retrospective - Drawing a fishbone diagram - Drawing a team mood chart - Drawing Face or Ice Cream for last working Sprint / Week
  • 16. ... Team Mood chart example Team members Day1 Day10
  • 17. 2. Development Practices - Scrum/Kanban board - Story analysis - Story tasking - Pair programming - Rotation - TDD - Cruise control
  • 18. Scrum / Kanban Board Backlog Story Analysis Development System Testing Delivered UX Dev QA UX Dev QA UX Dev QA UX Dev QA UX Dev QA UX Dev QA Dev pool QA pool
  • 19. Story Analysis - Before moving story from Backlog to Development - Adding sticky notes on story mentioning UX, Dev, QA UX - Dev - QA -
  • 20. Story Tasking - Should be done before moving story from Analysis to Dev - Dividing story into small tasks - Involving QA, so that task can be showcased to QA while working on story - to ease the pressure on QA at the end of the story Task 1 Task 2 Task 3 Task 4
  • 21. Pair Programming
  • 22. Pair Programming - Experiment with pairing developer with different technology & find out what works best for the team - UX (UI/Front-end/JavaScript) / Java - Java / Java - UX / UX - TDD / BDD
  • 23. ... - Pair Rotations Day 1 Day 2 Day 3
  • 24. ... - Pair Stations - Instead of individual machines - Collaborative desks - So that everyone can interact more with each other
  • 25. 3. Testing Practices - Continuous Integration - Continuous Delivery - Integration Testing - Variant Testing - alpha, beta & gamma environments
  • 26. Reference: http://agilitrix.com/wp-content/uploads/2009/08/agile-scrum-project-cycle.jpg
  • 27. Thank you

×