A New Introduction to Jira & Agile Product Management
•
9 recomendaciones•3,459 vistas
These are the corresponding slides from another one of my talks in the series for Great Product Teams: https://www.youtube.com/watch?v=TsG3OWTDAFY FOR MORE: If your team wants to learn more about building disruptive products, leveraging the power of data science, and exponential teamwork, check out my YouTube videos at: https://bit.ly/ChupSpeaks IN THIS PRESENTATION: In one video, I give you everything you need to understand the basics of Agile and get started in the new Jira interface! I'll show you basic Jira planning and working with Scrum and Kanban. We also talk about story points and about some of the most common customizations. With these basics, you'll get Jira to match the way your team works, so you and your team can focus on building great products.
Recomendados
Más contenido relacionado
La actualidad más candente
La actualidad más candente (20)
Similar a A New Introduction to Jira & Agile Product Management
Similar a A New Introduction to Jira & Agile Product Management (20)
Más de Dan Chuparkoff
Último
Último (20)
A New Introduction to Jira & Agile Product Management
- 1. A NEW INTRODUCTION TO JIRA & AGILE TEAM MANAGEMENT
- 2. A NEW INTRODUCTION TO JIRA & AGILE TEAM MANAGEMENT Dan Chuparkoff
- 3. @chuparkoff #DataSciFuture|Source: Licensed in 2018 to Dan Chuparkoff via Rich Chang Photography Innovative Product Leader Dan Chuparkoff https://twitter.com/chuparkoff https://youtube.com/c/DanChuparkoff https://linkedin.com/in/chuparkoff https://chuparkoff.com
- 4. + @chuparkoff #IntroToAgile| The ‘Project’ is JIRA’s highest level container. A single issue can only be in one JIRA Project at a time. JIRA PROJECTS
- 5. + @chuparkoff #IntroToAgile| The ‘Project’ is JIRA’s highest level container. A single issue can only be in one JIRA Project at a time. JIRA PROJECTS
- 6. + @chuparkoff #IntroToAgile| The ‘Project’ is JIRA’s highest level container. A single issue can only be in one JIRA Project at a time. JIRA PROJECTS
- 7. @chuparkoff | Don’t scatter your work into a million different fragments. Put all of your team’s work into a single JIRA Project. #IntroToAgile JIRA PROJECTS
- 8. @chuparkoff #IntroToAgile| Kanban Scrum TYPES OF AGILE All work Sprint A work Sprint B work Sprint C work
- 9. @chuparkoff #IntroToAgile| Kanban Scrum TYPES OF AGILE All work Sprint A work Sprint B work Sprint C work
- 10. @chuparkoff #IntroToAgile| Kanban Scrum TYPES OF AGILE All work Sprint A work Sprint B work Sprint C work
- 11. AGILE vs
- 12. @chuparkoff | #IntroToAgile KANBAN AGILE Kanban Agile is best for teams that are working on bugs or issues where most have an ASAP delivery schedule.
- 13. @chuparkoff | #IntroToAgile KANBAN AGILE Focus on rapid assignment and working in the right order not as much on estimating completion dates.
- 14. + @chuparkoff #IntroToAgile| collect all the work that needs to be done put the work in the right order assign and complete the work as fast as they can KANBAN AGILE
- 15. + @chuparkoff #IntroToAgile| collect all the work that needs to be done put the work in the right order assign and complete the work as fast as they can KANBAN AGILE
- 16. + @chuparkoff #IntroToAgile| collect all the work that needs to be done put the work in the right order assign and complete the work as fast as they can KANBAN AGILE
- 17. + @chuparkoff #IntroToAgile| collect all the work that needs to be done put the work in the right order assign and complete the work as fast as they can KANBAN AGILE
- 18. @chuparkoff | #IntroToAgile SCRUM AGILE Scrum Agile is best for teams that are working on new features with a tight schedule for finishing their work.
- 19. @chuparkoff | #IntroToAgile SCRUM AGILE Scrum teams manage their way toward this target by breaking their work up into iterative batches called sprints.
- 20. @chuparkoff | #IntroToAgile SCRUM AGILE When new work is discovered, the existing, in-progress work is left as it is and new work is added to the next sprint.
- 21. + @chuparkoff | collect all the work that needs to be done put the work in the right order define checkpoints for completion of batches of work then reprioritize at each checkpoint #IntroToAgile SCRUM AGILE
- 22. + @chuparkoff | collect all the work that needs to be done put the work in the right order define checkpoints for completion of batches of work then reprioritize at each checkpoint #IntroToAgile SCRUM AGILE
- 23. + @chuparkoff | collect all the work that needs to be done put the work in the right order define checkpoints for completion of batches of work then reprioritize at each checkpoint #IntroToAgile SCRUM AGILE
- 24. + @chuparkoff | collect all the work that needs to be done put the work in the right order define checkpoints for completion of batches of work then reprioritize at each checkpoint #IntroToAgile SCRUM AGILE
- 25. + @chuparkoff | collect all the work that needs to be done put the work in the right order define checkpoints for completion of batches of work then reprioritize at each checkpoint #IntroToAgile SCRUM AGILE
- 26. @chuparkoff | #IntroToAgile SMALL MANAGEABLE SNIPPETS Breaking work into fragments helps to ensure that ownership of every task is clear and that teams can reprioritize often.
- 27. @chuparkoff | #IntroToAgile SMALL MANAGEABLE SNIPPETS If your team is new to Agile methodologies, breaking tasks down is the most important thing to try first.
- 28. @chuparkoff | #IntroToAgile SMALL MANAGEABLE SNIPPETS This rapid, iterative delivery of progress is the thing that makes teams Agile in the first place.
- 29. ISSUES = TICKETS @chuparkoff | #IntroToAgile
- 30. @chuparkoff | #IntroToAgile KEEP IT SIMPLE Limit the number of required fields to the smallest number possible. Logging work should be quick and easy.
- 31. @chuparkoff | #IntroToAgile GRANULAR TASKS Try to break tasks down into small enough fragments that you can reprioritize as often as you discover new things.
- 32. + @chuparkoff #IntroToAgile| a single Agile task should take at least a few hours a single Agile task should not take more than 3 days As you begin to master Agile, try making the maximum amount of time for a task 1 day AGILE TASKS
- 33. + @chuparkoff #IntroToAgile| a single Agile task should take at least a few hours a single Agile task should not take more than 3 days As you begin to master Agile, try making the maximum amount of time for a task 1 day AGILE TASKS
- 34. + @chuparkoff #IntroToAgile| a single Agile task should take at least a few hours a single Agile task should not take more than 3 days As you begin to master Agile, try making the maximum amount of time for a task 1 day AGILE TASKS
- 35. + @chuparkoff #IntroToAgile| a single Agile task should take at least a few hours a single Agile task should not take more than 3 days As you begin to master Agile, try making the maximum amount of time for a task 1 day AGILE TASKS
- 37. @chuparkoff | #IntroToAgile STORIES Stories are usually used by Product Managers to describe planned work for a specific feature of a product.
- 38. @chuparkoff | #IntroToAgile TASKS Tasks are typically used by any team members to describe other planned, non-Story work.
- 39. @chuparkoff | #IntroToAgile BUGS Bugs can be used to explicitly call out unplanned work. This helps when you are working improve your overall quality.
- 40. @chuparkoff | #IntroToAgile EPICS An Epic is a collection of Stories & Tasks arranged together to achieve some specific, noteworthy outcome.
- 41. CUSTOMIZING ISSUE DETAILS @chuparkoff | #IntroToAgile
- 42. @chuparkoff | #IntroToAgile ADDING STORY POINTS The Story Points field is useful when trying to estimate work during Scrum planning.
- 44. @chuparkoff | #IntroToAgile LABELS Labels are just tags. Users can make their own Labels on-the-fly while editing a ticket.
- 45. @chuparkoff | #IntroToAgile COMPONENTS Components are also tags. New Components must be created by an administrator in JIRA’s Settings section.
- 46. LET’S ACTUALLY DO SOME WORK @chuparkoff | #IntroToAgile
- 47. @chuparkoff | #IntroToAgile THE SCRUM BACKLOG In the Scrum Backlog, you prioritize your team’s work and arrange it into two-week delivery batches called Sprints.
- 48. @chuparkoff | #IntroToAgile THE SCRUM BACKLOG In the Scrum Backlog, you prioritize your team’s work and arrange it into two-week delivery batches called Sprints. (There is no Backlog in Kanban - for Kanban projects, you can jump ahead to the section on Boards)
- 49. @chuparkoff | #IntroToAgile THE SCRUM BACKLOG In the Scrum Backlog, you prioritize your team’s work and arrange it into two-week delivery batches called Sprints.
- 50. + @chuparkoff #IntroToAgile| A Sprint has a start date and an end date Sprints are often 2 weeks long AGILE SPRINTS While a sprint is active, you shouldn’t add new work to the active sprint
- 51. + @chuparkoff #IntroToAgile| A Sprint has a start date and an end date Sprints are often 2 weeks long AGILE SPRINTS While a sprint is active, you shouldn’t add new work to the active sprint
- 52. + @chuparkoff #IntroToAgile| A Sprint has a start date and an end date Sprints are often 2 weeks long AGILE SPRINTS While a sprint is active, you shouldn’t add new work to the active sprint
- 53. + @chuparkoff #IntroToAgile| A Sprint has a start date and an end date Sprints are often 2 weeks long AGILE SPRINTS While a sprint is active, you shouldn’t add new work to the active sprint
- 54. @chuparkoff | #IntroToAgile EPICS When creating Epics, avoid long-running / unfinishable epics like ‘Maintenance’ and ‘Refactoring’.
- 55. @chuparkoff | #IntroToAgile In Agile, we estimate work using StoryPoints. StoryPoints are just a relative measure of complexity: 13 is harder than 5. STORY POINTS
- 56. WHEN ESTIMATING USE: 1, 2, 3, 5, 8, or 13 @chuparkoff | #IntroToAgile
- 57. @chuparkoff | #IntroToAgile If your whole team is new at this, your team velocity might not make sense. You’ve got to find a way to calibrate. STORY POINTS
- 58. TROLL ALERT! @chuparkoff | #IntroToAgile
- 59. + @chuparkoff #IntroToAgile| Your smallest estimate ever should be 2-3 hours or 1 point STORY POINT CHEATING Your biggest estimate ever should be 3 days or 13 points New teams can use these two boundary points as a guide
- 60. + @chuparkoff #IntroToAgile| Your smallest estimate ever should be 2-3 hours or 1 point STORY POINT CHEATING Your biggest estimate ever should be 3 days or 13 points New teams can use these two boundary points as a guide
- 61. + @chuparkoff #IntroToAgile| Your smallest estimate ever should be 2-3 hours or 1 point STORY POINT CHEATING Your biggest estimate ever should be 3 days or 13 points New teams can use these two boundary points as a guide
- 62. + @chuparkoff #IntroToAgile| Your smallest estimate ever should be 2-3 hours or 1 point STORY POINT CHEATING Your biggest estimate ever should be 3 days or 13 points New teams can use these two boundary points as a guide
- 63. STARTING THE SPRINT @chuparkoff | #IntroToAgile
- 64. + @chuparkoff #IntroToAgile| All tasks in the project should go through all the steps of the workflow JIRA WORK FLOWS Users should be able to see all of the columns of the workflow, so keep the number of steps to 7 or less.
- 65. + @chuparkoff #IntroToAgile| All tasks in the project should go through all the steps of the workflow JIRA WORK FLOWS Users should be able to see all of the columns of the workflow, so keep the number of steps to 7 or less.
- 66. + @chuparkoff #IntroToAgile| All tasks in the project should go through all the steps of the workflow JIRA WORK FLOWS Users should be able to see all of the columns of the workflow, so keep the number of steps to 7 or less.
- 67. @chuparkoff | #IntroToAgile If your whole team is new at this, your team velocity might not make sense. You’ve got to find a way to calibrate. ONE BOARD
- 68. @chuparkoff | #IntroToAgile Make sure a single person on your team only needs to care about one project and one board in JIRA at a time. 1 BOARD TO RULE THEM ALL
- 75. DAN CHUPARKOFF Follow this YouTube channel for more Build Great Software videos
- 76. DAN CHUPARKOFF Follow this channel for more Building Great Software videos