Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Project & Portfolio Management Using JIRA Software
Similar to Project & Portfolio Management Using JIRA Software (20)
Recently uploaded
Recently uploaded (20)
Project & Portfolio Management Using JIRA Software
- 1. HTTPS://AUG.ATLASSIAN.COM/SYDNEY Atlassian User Group Project & Portfolio Management Using JIRA Software
- 2. Agenda Welcome Speakers Presentation by Robin Scanlon Presentation by Trevor Vella Q & A Closing notes
- 3. Sponsor Sponsor food/drinks, swag or venue to showcase your business. Speak Speak at AUG event to share insights, tips and best practices with user community. Engage Connect with the Atlassian user community of more than 15,000 people in more than 30 countries. Welcome – Sydney AUG
- 4. Trevor Vella Trevor is currently the Development Practice Manager at Transport for NSW and has over 25 years of IT experience. Day to day, he champions the development and evolution of continuous delivery capability and a DevOps mentality throughout the organisation. Robin Scanlon A Portfolio buff and Atlassian Expert. He’s been consulting and training people in the software world for 10 years, particularly in the project management space. Originally from Scotland, he now calls Sydney home, and when not at work can be found running or drinking wine. Speakers
- 5. Portfolio for JIRA How to set yourself up for success ROBIN SCANLON | GLINTECH
- 6. PLAN TO PLAN
- 7. WHAT’S YOUR PLANNING CYCLE?
- 8. Demo
- 10. DATA QUALITY rubbish in = rubbish out
- 11. START SMALL
- 12. VISIBILITY
- 13. Structure for JIRA Story mapping simplified TREVOR VELLA | TRANSPORT FOR NSW
- 14. 14 Story Mapping was invented by Jeff Patton
- 15. Story maps are about Saving the Story in Agile Development - JEFF PATTON 15
- 16. Story aps fo us o u dersta di g usto ers’ o je tives and jobs-to-be-done. It’s not about generating stories or creating a release plan. 16 Why Story Mapping? Images courtesy Jeff Patton: User Story Mapping: Discover the whole story; build the right product.
- 17. People and Corporate Services | 17 Shared understanding and alignment are objectives of collaborative work Shared documentation != Shared Understanding
- 18. People and Corporate Services | 18 Communication & Feedback Maintain the richest communication possible
- 19. People and Corporate Services | 19 Story Mapping Overview
- 21. Story maps solve one of the big problems with using user stories in agile development – that’s losing sight of the ig pi ture. - JEFF PATTON 21
- 22. 22 Story Mapping help to conceptualise how User Tasks meet underlying Goals
- 25. 25 A Real Life Transport Story Map The backbone
- 26. 26 How we started the conversation
- 27. 27 Story Mapping on a Wall
- 28. Enter Structure for JIRA. 28
- 29. Headline Features Generate trip plans Receive travel alerts Download timetables Live traffic information Transport fare deals Lost property 29 Meet transportnsw.info
- 30. 30 A Real-Life Story Map… i Stru ture!
- 31. 31 Drilling into User Activities Create issue hierarchies of arbitrary depth – these are all Epics! Epic Type custo field helps to classify i JQL searches
- 32. 32 Drilling into Features Resolution tells Structure when an issue is complete
- 34. 34 Back to the top level Completion rolls up from Stories & Tests to give an overall, higher level view of progress on Big Activities.
- 35. 35 Reporting is configurable Map custom and/or multiple workflows to completion % and weighting of issues
- 36. 36 Keep the big picture in mind
- 37. QUESTIONS?
Editor's Notes
- Story maps solve one of the big problems with using user stories in agile development – that’s losing site of the big picture. Story maps look at a product or feature from the users’ perspective. Building a story map asks the story mapper to think through the experience of using the product from their users’ perspective. And, it turns out that solves a lot of problems with software development.
- Story maps are a tool developed by Jeff Patton, User Story Mapping. As Patton states, “Your software has a backbone and a skeleton — and your map shows it.” Story maps help with planning and prioritising by visualizing the solution as a whole. Story mapping is not designed to generate stories or create a release plan — it is about understanding customers’ objectives and jobs-to-be-done. Story maps provide an effective means to communicate the narrative of our solution to engage the team and wider stakeholders and get their feedback. By going through story maps and telling the story of the solution, we ensure that we have not missed any major components. At the same time, we maximise learning by identifying the next riskiest hypothesis to test while minimising waste and over engineered solutions that do not fit customer needs as defined in our MVP.
- This in turn leads to a better sense of purpose during the design, and keeps the mind of everyone from the analyst to the developer on the big picture. This deeper understanding of design motivation will help a delivery team feel in creative control for a project, and helps facilitate innovation at every stage of the project.
- Physical walls look great, but now we need some kind of backup for falling post-it’s
- The best way we can talk through our usage of JIRA structure is to walk you through one of our current projects! Meet transportnsw.info, our poster child for the evening. We’ll be taking a look through the project structure and how it supports some of the core Story Mapping concepts.
- Bit of trivia… there are almost 1300 issues summarised in the picture above! Imagine trying to corral that on a physical wall board!
- Structure can span multiple custom workflows comfortably – just define what each status means to the delivery team as a high level completion percentage and you’re good to go! If your decomposition is not reasonably homogenous, you can weight an issues contribution to the ‘roll-up’ by it’s story point or time estimate value.
- Every issue all the way down to the bottom will show it’s place in the chain up to high-value ‘Big Features’. This helps keep everyone’s mind on the ultimate goal they are trying to accomplish, and encourages implementers to think about how they are meeting the actual user goal at every phase of the development process.
- **For the ‘Thank you’ slide, simply choose the same master slide as the intro card and delete the subtitle (unless you need it for good reason).