Your SlideShare is downloading. ×
Getting agile
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

Getting agile

105
views

Published on


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

  • Be the first to like this

No Downloads
Views
Total Views
105
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
2
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
  • But Agile is more than this...
  • February 2001, 17 software developers [5] met at the Sno wbird, Utah re sort, to discuss lightweight development methods. They published the Manifesto for Agile Software Development
  • An oversimplified version of Agile. Nutshell. Agile is a philosophy, and idea.
  • Scrum is a way of implementing Agile. In 1986, Hirotaka Takeuchi and Ikujiro Nonaka de scribed a new approach to commercial product development that would increase speed and flexibility called rugby approach as the whole process is performed by one cross-functional team across multiple overlapping phases, where the team "tries to go the distance as a unit, passing the ball back and forth". [
  • Pigs & chickens
  • Always ends with a shippable product
  • Product logs (epic story) - breakdown to user stories, estimation and backlog filling.
  • Sprint commences with a backlog and daily standup meetings - 15 mins.
  • Each answers 3 questions.
  • Agree on DoD early - success criteria.
  • Everyone’s invited What’s been accomplished - new, support training, etc
  • 30 mins. Scrum team participates. Start doing/Stop doing/Keep doing.
  • End result - consistent delivery of shippable product every sprint.
  • What practical implementation are we adopting?
  • Kanban ( 看板 ? ), also spelled kamban , and literally meaning " s ignboard " or " billboard " , is a co ncept related to lean and just-in-tim e (J IT) prod uction. Acco rding to Taiichi Ohno , the man credited with developing Just-in-time, kanban is one means through which JIT is achieved. [2][3] - visualisation technique. To visualise a p rocess. Kanban helps visualises a time-boxed Scrum process
  • Kanban represents 2 weeks process flow (visualisation) Developers take stories from backlog to In Dev, to Review...
  • Note on Review column. Only QAs and POs are allowed to move to ‘Done’. Otherwise, it goes through day-to-day cycle of working on one story at a time. As in our earlier Scrum process breakdown.
  • End: We’ve talked a lot about user stories....
  • what are the key ingredients of a user story?
  • Absolutely crucial a story captures the end result - what user wants to achieve. Magnet story - too focused on implementation details. Begin with the end in mind. So how do we know the implementation details?
  • Note: QA plays important role in stage one - details from PO Success criteria must be identified and approved and placed at the BACK of the card.
  • But we still need to track our work, issues and commits....
  • Tickets can contain - QA’s test plans, success criterias, screenshots, tech specs, etc Kanban should contain only backlog for that particular sprint
  • Process have been simplified.
  • Open = Backlog In Progress = In Dev Approval = Review Resolved = Done
  • Transcript

    • 1. Getting AgileIntroduction to Agile with Scrum
    • 2. Agile is...• iterative and incremental development• adaptive planning• evolutionary development & delivery• responsive development
    • 3. Agile is...• philosophy• ideology• way of life
    • 4. The Agile ManifestoIndividuals &Individuals &interactionsinteractionsIndividuals &Individuals &interactionsinteractionsWorking softwareWorking softwareWorking softwareWorking softwareCustomerCustomercollaborationcollaborationCustomerCustomercollaborationcollaborationResponding to changeResponding to changeResponding to changeResponding to changeProcesses & toolsProcesses & toolsProcesses & toolsProcesses & toolsComprehensiveComprehensivedocumentationdocumentationComprehensiveComprehensivedocumentationdocumentationContract negotiationContract negotiationContract negotiationContract negotiationFollowing to a planFollowing to a planFollowing to a planFollowing to a planoveroveroverover
    • 5. What about Scrum?
    • 6. What is Scrum?
    • 7. Goals of Scrum• it is about moving as a team• is results oriented• is commitment driven
    • 8. Roles in Scrum• ScrumMaster - governance• Product Owner - stakeholders• Team - cross-functional group of doers
    • 9. Scrum Process
    • 10. Scrum BreakdownSprintSprintplanningplanningSprintSprintplanningplanning Daily ScrumDaily ScrumDaily ScrumDaily Scrum ReviewReviewmeetingmeetingReviewReviewmeetingmeeting RetroRetroRetroRetro
    • 11. Scrum BreakdownSprintSprintplanningplanningSprintSprintplanningplanning Daily ScrumDaily ScrumDaily ScrumDaily Scrum ReviewReviewmeetingmeetingReviewReviewmeetingmeeting RetroRetroRetroRetro
    • 12. Scrum BreakdownSprintSprintplanningplanningSprintSprintplanningplanning Daily ScrumDaily ScrumDaily ScrumDaily Scrum ReviewReviewmeetingmeetingReviewReviewmeetingmeeting RetroRetroRetroRetro
    • 13. Scrum BreakdownSprintSprintplanningplanningSprintSprintplanningplanningDaily ScrumDaily ScrumWhat did you do yesterday?What did you do yesterday?What are you doing today?What are you doing today?Any blockers?Any blockers?Not status updates, butNot status updates, but commitmentcommitment..Daily ScrumDaily ScrumWhat did you do yesterday?What did you do yesterday?What are you doing today?What are you doing today?Any blockers?Any blockers?Not status updates, butNot status updates, but commitmentcommitment..ReviewReviewmeetingmeetingReviewReviewmeetingmeeting RetroRetroRetroRetro
    • 14. Scrum BreakdownSprintSprintplanningplanningSprintSprintplanningplanningDaily ScrumDaily ScrumDev & QA obtain details from PODev & QA obtain details from PODev, test, stage (local)Dev, test, stage (local)Feedback from PO/QAFeedback from PO/QADone (DoD)Done (DoD)Daily ScrumDaily ScrumDev & QA obtain details from PODev & QA obtain details from PODev, test, stage (local)Dev, test, stage (local)Feedback from PO/QAFeedback from PO/QADone (DoD)Done (DoD)ReviewReviewmeetingmeetingReviewReviewmeetingmeeting RetroRetroRetroRetro
    • 15. Scrum BreakdownSprintSprintplanningplanningSprintSprintplanningplanningDaily ScrumDaily ScrumDaily ScrumDaily ScrumReviewReviewmeetingmeetingReviewReviewmeetingmeeting RetroRetroRetroRetro
    • 16. Scrum BreakdownSprintSprintplanningplanningSprintSprintplanningplanning Daily ScrumDaily ScrumDaily ScrumDaily Scrum ReviewReviewmeetingmeetingReviewReviewmeetingmeeting RetroRetroRetroRetro
    • 17. Scrum BreakdownSprintSprintplanningplanningSprintSprintplanningplanning Daily ScrumDaily ScrumDaily ScrumDaily Scrum ReviewReviewmeetingmeetingReviewReviewmeetingmeeting RetroRetroRetroRetro
    • 18. Scrum Process
    • 19. So, what’s next?
    • 20. Goodbye Jira
    • 21. Hello Kanban
    • 22. BeginningBacklogBacklogBacklogBacklog In DevIn DevIn DevIn Dev ReviewReviewReviewReview DoneDoneDoneDone DeployedDeployedDeployedDeployed2 weeks
    • 23. BeginningBacklogBacklogBacklogBacklog In DevIn DevIn DevIn Dev ReviewReviewReviewReview DoneDoneDoneDone DeployedDeployedDeployedDeployed2 weeks
    • 24. Scrum RecallSprintSprintplanningplanningSprintSprintplanningplanningDaily ScrumDaily ScrumWhat did you do yesterday?What did you do yesterday?What are you doing today?What are you doing today?Any blockers?Any blockers?Not status updates, butNot status updates, but commitmentcommitment..Daily ScrumDaily ScrumWhat did you do yesterday?What did you do yesterday?What are you doing today?What are you doing today?Any blockers?Any blockers?Not status updates, butNot status updates, but commitmentcommitment..ReviewReviewmeetingmeetingReviewReviewmeetingmeeting RetroRetroRetroRetro
    • 25. End of SprintBacklogBacklogBacklogBacklog In DevIn DevIn DevIn Dev ReviewReviewReviewReview DoneDoneDoneDone DeployedDeployedDeployedDeployed
    • 26. End of SprintBacklogBacklogBacklogBacklog In DevIn DevIn DevIn Dev ReviewReviewReviewReview DoneDoneDoneDone DeployedDeployedDeployedDeployed2 weeks
    • 27. Storytelling
    • 28. User Story
    • 29. User Story• written in end user’s language• captures what end user wants to achieve• "As a <role>, I want <goal/desire> so that<benefit>"• simple wireframe, success criteria
    • 30. Scrum RecallSprintSprintplanningplanningSprintSprintplanningplanningDaily ScrumDaily ScrumDev & QA obtain details from PODev & QA obtain details from PODev, test, stage (local)Dev, test, stage (local)Feedback from PO/QAFeedback from PO/QADone (DoD)Done (DoD)Daily ScrumDaily ScrumDev & QA obtain details from PODev & QA obtain details from PODev, test, stage (local)Dev, test, stage (local)Feedback from PO/QAFeedback from PO/QADone (DoD)Done (DoD)ReviewReviewmeetingmeetingReviewReviewmeetingmeeting RetroRetroRetroRetro
    • 31. User Story
    • 32. Long live JiraDidn’t really think we’d ditch Jira, did ya?
    • 33. Integrating Jira• this is a business after all...• serves as a comm & management tool• serves as record for commits• Introducing Greenhopper
    • 34. Integrating Jira
    • 35. Integrating Jira
    • 36. So, what’s next?
    • 37. Small steps• turn Jira into user stories - create ourbacklog. Use Greenhopper.• read more about Agile and Scrum• start our first sprint on Monday• slowly introduce more Agile in an Agile way
    • 38. Coming Sessions• Important Agile practices• SCM practices, paired programming• CI, CD,TDD/BDD, etc• War stories (experiences with Agile)• Videos
    • 39. Thank you.

    ×