With this configuration, the team can maintain focus on the immediate work instead of endlessly scrolling through the an unplanned backlog. Epics can still be used to manage the board. Now the team can drag issues from the Backlog into an In-Progress status and they will appear on the Kanban board. I like how removing all statuses from the To-Do column keeps Open issues on the backlog. I snagged a few screenshots from the presentation to highlight how a Kanban backlog can be configured. The KanPlan presentation was a useful presentation and hands-on lab that demonstrated how teams can use a mixed methodology by changing JIRA filters and boards. In other cases, the team still wants to use epics to categorize the backlog but deliver using Kanban. As a product backlog grows, the To-Do list can become overwhelming when viewing the JIRA board. Teams often find themselves in the middle of being “Wagile” – Waterfall and Agile as they continue along their Agile journey.įor example, a project team may implement Kanban but also want to maintain and groom a backlog of user stories. Kanban as models for delivering solutions. These power ups let you leverage Trello for the high level roadmap planning while implementing the roadmap in JIRA and Confluence.Īgile teams continue to balance using Scrum vs. Trello also integrates easily with Confluence and JIRA using these Power Ups capabilities. Trello also supports voting so a community of users can vote for their favorite features to drive priority. As features get planned and accepted into the development roadmap, they can be transitioned to JIRA for software development and execution.Ī Trello board can also be used to groom user stories as the move from ideas, requirements, estimation and eventually becoming a release candidate. It is a helpful tool to perform high level roadmap planning. The Trello board provides an Inbox column to capture incoming requests that need to be categorized. The superpower to solve feature request management is to use Trello to track feature requests.Ī Trello board can be used to capture feature requests and then categorize and prioritize them for action or for future consideration Some feature requests will go into a backlog but won’t even make it on to a product’s near term roadmap or release plan. Keeping track of feature requests can be difficult as new requests come from many different sources. JIRA Service Desk includes a pre-built widget that can collect the feedback. Product managers can include a link to integrate directly with JIRA Software or Service Desk to capture the feedback. Collect product feedback using JIRA Service Desk or JIRA Software.Īs new products are deployed, obtaining real-time feedback from customers can be difficult to obtain. It becomes a living document to update as the problem is explored Involves the whole team through comments. The project poster is a useful tool similar to a project charter the helps to align everyone to the problem definition, scope and potential solutions. One useful “play” is the project poster at Several noteworthy superpowers includes: Create a Project Poster in Atlassian ConfluenceĪtlassian provides many free templates and techniques in their Team Playbook. His presentation provided examples on how Atlassian tools are a product owner’s superpowers. formatting a PowerPoint presentation)ĭuring the Atlassian Summit, Phil Oye presented Atlassian’s 4 Pillars for Product Managers and how Trello, Confluence and JIRA can support product managers. (It was a lot faster too using the Confluence page format vs. I’ve applied this technique to providing status updates, conducting my staff meetings and even presented my Key Summit Takeaways as a Confluence page.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |