Ce diaporama a bien été signalé.
Nous utilisons votre profil LinkedIn et vos données d’activité pour vous proposer des publicités personnalisées et pertinentes. Vous pouvez changer vos préférences de publicités à tout moment.

A story about scrum team

A story about scrum team

Livres associés

Gratuit avec un essai de 30 jours de Scribd

Tout voir
  • Soyez le premier à commenter

  • Soyez le premier à aimer ceci

A story about scrum team

  1. 1. A Story About Scrum team Chapter - JIRA 1
  2. 2. © Benzne. All rights reserved 2 About Us Stability is a flux “Lotus is a an extension of that same concept of equilibrium, of beauty amidst chaos, it is self regenerating, self existent, continuously reproduced from its own matrix, each petal opening is progressive unfolding of our path to end state, negotiating the murky, muddy waters to realise one's own potential.” “Benzne aims to enable organizations and individuals in their journey to constantly innovate and reinvent themself, to help them be agile, open, looking forward to accept change, continuously evolving and yet be in equilibrium, to somehow be in a state of constant flux and yet be stable, much like a Benzene ring.”
  3. 3. About the speaker Anuj M Ojha Agile Consultant An experienced Agile practitioner and transformation consultant who helps organizations deliver value to customers and businesses, through team coaching and mentoring, effective collaboration, facilitation and continuous improvement practices Certifications Experience 14+ years of experience with relevant agile experience of 11+ years and have trained 12000+ participants & coached 80+ teams on agile practices & implementation techniques. Have been to various geographies to deliver consulting services. My special area of interest has been bringing in business agility, appropriate mindset & enriching Culture. It all starts from no process to some process which helps teams & companies in being their own better version by healing their broken processes and other aspects. Educational Experience • Bachelor of Engineering Areas of Expertise Business Agility, Agile Coaching (Leadership, Business Stakeholders, Product Owners, Scrum Masters, Development Team members, Agile in Distributed Teams & at Scale, Agile Engineering Practices Organisations I have consulted ServiceNow, McKinsey, Verifone, Sunlife Financial, Honeywell, Fidelity, SAP Labs, Grab, Sourcebits, Dell, Dell EMC, Nets Norway, Maersk, NEC Technologies, Reliance JIO, Reliance ADA, Ericsson, Orange, L&T Infotech, Gemalto and many more.
  4. 4. Today we are going to talk about the Scrum Team & also their JIRA experience.. PAM Product Owner SAM Scrum Master DAM Development Team
  5. 5. We used various physical Visual Indicators.. .. and were also happy while we wanted to go digital as we were also facing some limitations.. .. like working in distributed team, archiving our work, multi team work, focus more on creating values then managing board..
  6. 6. Key Questions ● Can we get the online board like the visual board that we have been using? ● We use diff. color codes today to differentiate various issue types? ● Can we immerse our DOD in different columns? ● Can we showcase risk and dependencies? ● Will it help us in reducing our manual work?
  7. 7. The journey begins PDCA ● Plan mode for backlog management ● Active Sprint mode to assure delivery ● Report mode for tracking progress ● Dashboard for quick glance ● Filters to find anything 7
  8. 8. We want this from JIRA 8 PLAN RELEASE REPORT TRACKJIRA
  9. 9. © Benzne. All rights reserved Feature I Feature H Feature G Feature F Feature C Feature B Iterative & Incremental approach Project Start Project End Sprint Feature H Feature G Feature F Feature E Feature D Feature C Feature B Feature A Feature A Sprint Feature E Feature D Feature C Feature B Feature A Feature A Sprint Sprint Feature E Feature D Feature C Feature B Feature A Sprint Sprint Feature I Feature H Feature G Feature F Feature E Feature D Feature C Feature B Feature A “Definition of Done” Coded, Reviewed, Tested, Integrated & Documented Pre Release Sprint
  10. 10. © Benzne. All rights reserved Potentially Shippable Product Increment Review No Changes in Duration or Goal Retrospective Team Daily Scrum Meeting Product Owner Input from End-Users, Customers, Team and Other Stakeholders Product Backlog Refinement Scrum Master SCRUM FRAMEWORK Product Backlog Sprint Backlog Sprint 1-4 Weeks 8 9 10 11 12 7 1 2 3 4 5 6 “The Scrum Team” Sprint Planning Meeting Team Selects How Much To Commit To By Sprint’s End 7 1 2 3 4 5 6
  11. 11. PLANVersion, Backlog – Product/ Sprint, Create issues, prioritize, estimation, product planning, sprint planning, backlog grooming, progressive elaboration 11
  12. 12. JIRA Board - Yet-to-start view 12 1. Switch panels - plan, board & report 2. Maintain backlog 3. Manage sprints - current and future 4. Board Configurations
  13. 13. Backlog Mode - It has total 3 panels - Version, Epic and Backlog - Version - Create a version which you are currently working on and also other future versions if you want to. - Epic - The bigger stories are called EPICS which is further on broken into small stories which when refined further to get done into sprints. Here we can add issues which could be Story, Bug, Tasks or other type - Backlog - here you manage the list of issues that you want to finish in a version which you can also categorize into sprints and the active sprints are always at the top and the orders of issues should also signify their priority 13
  14. 14. Create a version - Expand the VERSIONS panel by clicking on it - Click on link - Hover the cursor on Versions heading and you will get the link to create version. 14
  15. 15. Create EPICs - Now it’s time to create the backlog first which is done by identifying the high level stories or say the requirements that are bigger in size also called EPICs. - There are 2 ways of creating it. One is to click on CREATE button in Navigation panel. - Same like Versions, click on the EPICS panel and hover the cursor on EPICS heading to get the CREATE EPIC link. Click on it and fill up the following details: 15
  16. 16. Create Issues in EPIC - Once the issue is created then the entry will be updated in EPICS panel - To create issue in an EPIC, either you can create it through CREATE button from Top Navigation Panel or simply expand the Epic and click on CREATE ISSUE IN EPIC link. 16
  17. 17. Create an issue in Epic - Fill up all the entries - Issue type shall be story in EPICs - Labels will help us in segregating the issues by creating filters 17
  18. 18. Epic looks like this : When stories are not part of current sprint 18
  19. 19. Epic looks like this : When stories are part of current sprint 19
  20. 20. BACKLOG MUST BE READY FIRST 20
  21. 21. Now it’s time to start the sprint First step : Create a new sprint // update the sprint name and number 21
  22. 22. Move the items from the Backlog to the sprint created 22
  23. 23. Ensure all the stories planned are moved in the corresponding sprint before starting the Sprint planning meeting - In sprint planning meeting, product owner educates the team about planned stories - Team discusses the details of all the stories till they get clarity and confidence on creating the technical tasks to complete the stories - Recommendation is to create the technical tasks as sub-tasks in corresponding story : this is useful when you are only doing story point estimations - When you are estimating in hours, better you not create the sub-task and instead create the tasks and link them to stories. BECAUSE – currently jira is not supporting the sum of estimates of sub-tasks as the Original Estimate task 23
  24. 24. Create sub-task in a story Story description and all other options can be viewed in the right-most panel which only get appeared once the story is clicked 24
  25. 25. Create sub-task in a story ● Click on the CREATE SUB-TASK Button ● Enter all the relevant details. ● You can attach the documents and also assign the tasks if needed. ● Please fill in the estimates 25
  26. 26. DOActive sprint mode, columns, daily updates, daily stand up, board configuration 26
  27. 27. Start the sprint Remember, the sub-tasks are not visible on BACKLOG mode but they can be viewed once you go into corresponding stories and also on ACTIVE SPRINT mode if the story is part of the current sprint. Also, sum of estimates of all the stories should not exceed the capacity planned for team so as to avoid over expectations. Click on the START SPRINT button so as to view the items in Sprint backlog on ACTIVE SPRINT mode. Select the start date and end date of sprint before clicking on START SPRINT. 27
  28. 28. Active Sprint Mode ● New Items in the backlog moves to To Do which are yet to be started ● Items from previous sprints if any will rest in their respective states. ● Each column signifies the current state of item. ● A story gets moved to DONE only when all the sub-tasks & linked items are moved to DONE otherwise the story stays UNDONE and goes to the next sprint for completion 28
  29. 29. Daily Standup 29
  30. 30. Remember: Story is done only when all sub-tasks & linked items are done Legends: Sprint name, includes goal, timer, columns, swimlanes, quick filters, board setting option, complete sprint, expand view for task or stories, tickets – assignee, estimate, priority, type of issue, unique id 30
  31. 31. Board Setting 31
  32. 32. Swimlanes Quick Filters 32
  33. 33. Card Colors 33 Card layout
  34. 34. Estimate – Original time estimate or Story points 34
  35. 35. Working days 35
  36. 36. TRACK Filters, Reports & Charts at different levels 36
  37. 37. Filters Select project, issue type, assignee, specific text, date range, columns in result view, detailed view, listicle view, export options 37
  38. 38. Filters 38 FieldsOperators Functions
  39. 39. Dashboard : Few gadgets to recommend 39 Two dimensional filter statisticPie Chart - AssigneesPie Chart - Statuses Created Vs ResolvedSprint Health
  40. 40. Agile reports 40
  41. 41. Issue Analysis Reports 41
  42. 42. Forecast Management & other 42
  43. 43. Sprint Burndown Chart 43
  44. 44. Sprint Burndown Chart 44
  45. 45. Velocity Chart 45
  46. 46. Cumulative graph 46
  47. 47. Version Report 47
  48. 48. Version Report 48
  49. 49. Control Chart 49
  50. 50. Release Burndown // when you align sprints at the base of the chart 50
  51. 51. Release Burndown // when you align sprints at the base of the chart 51
  52. 52. Releases Mode 52
  53. 53. Epic Burndown chart 53
  54. 54. © Benzne. All rights reserved Let’s get the basics right 54
  55. 55. Board, we are not saying you goodbye.. 55
  56. 56. © Benzne. All rights reserved In Sprint Review, cleaning the board by removing DONE stories 56
  57. 57. © Benzne. All rights reserved In Sprint planning, Check the UNDONE stories from previous sprint & new stories from current sprint 57
  58. 58. © Benzne. All rights reserved Prioritise backlog, splitted down to tasks, finish estimation 58
  59. 59. © Benzne. All rights reserved Step 5 - And everything should have a meaning like... Team name, Sprint#, Start date & End date of sprint Color codes like post-it color signifies its a story or task or kind of task and also distinguishes different goals. Each post it also has estimates like stories have story points and tasks have hours We keep our primary focus towards achieving the sprint goals over finishing only specific tasks Definition of Done helps us in knowing all the necessities that confirms the quality and shared understanding towards work COMPLETION 59
  60. 60. THANK YOU www.Benzne.com

×