Jump to content
Search In
  • More options...
Find results that contain...
Find results in...

Recommended Posts

  • Owner

Regardless if you work in a continuous delivery flow like Kanban, a sequential delivery flow like waterfall or an iterative delivery flow like Scrum, you will benefit greatly from having portfolio management. Having a dedicated funnel ensures that you get a proper overlook of your incoming request. In this article we will discuss how that can be done by creating a process for it in Jira Software.

Advanced Roadmaps is a very useful tool because it allows us to get the big picture. It also allows us to scale the hierarchies in Jira for issue types. This is important because the standard hierarchies are designed for teams, so they do not scale well. While you can work around this using the sideways approach where you have the higher hierarchies in a separate project and link between them, that is not really a hierarchy. This also works poorly when you wish to display things in Advanced Roadmap.

The first thing we need to do for a proper hierarchy view in Advanced Roadmaps is to define the portfolio levels. We need to accommodate for multiple scenarios as requests, or demands, often come in different forms. The most common types are projects or even programs, or new features. We also want to make sure we can work with the different frameworks out there, so we add a collaboration level as well as defined in SAFe.

To avoid a lot of confusion between different frameworks and other tools, we rename the Epic issue type in Jira Software to Feature. It will not be perfect, but it will have to do until we get the ability to rename it properly when Atlassian makes that change in the future.  We do this by going to Issues -> Issue Types and edit the Epic issue type. We also add two new issue types for Initiative and Capability.

Next we go to Plans -> Settings -> Advanced Roadmaps hierarchy configuration. There we add two new levels called Initiative and Capability and map them with our newly created issue types with the same names. Finally, we rename the Epic to Feature, and we should have our first hierarchy defined. We can go back and adjust this later if we want. The setup should now look like this:

Screenshot 2021-01-05 at 18.33.49.png

We can now add this to our projects by adding the issue types to our Issue Type Schemas. Depending on your setup you may want the new issue types for Initiative and Capability to exist in a separate Issue Type Schema, or you will add them to the standard schema. Either way we still need to give the new issue type a workflow that match their purpose. So we head over to Issues -> Workflows and create a new workflow.

Again we want to consider what the purpose of these issue types is and who will actually work with them. Initiative, Capability and Feature are all used by management and requirement analysts to provide information on how to realize demands. That means that we do not have the same transfer of responsibility as for User Stories. Instead, we need to consider what we actually do in the portfolio and what we need to track in terms of activities.

SAFe have a pretty good example of this for their Portfolio Kanban. Their first step is Funnel and for us that is pretty much everything that comes into our workflow, and we define this as new. Anything that comes in to the portfolio needs to be reviewed to see what we should focus on next. Since we will not review everything we add two steps for the review process: Ready for Review and In Review. This allows us to only pick things that we want to review by moving them from new to Ready for Review, and then we have an active status to indicate that we are working on this.

We do the same for Analysis, which is the step where we involve Business Analysts and Requirement Analysts to define the need in more detail. For this we add Ready for Analysis for when the Review process lead to us spending time to break down the need in a requirement process. We also add the In Analysis to indicate that it has entered the Requirement process.

Before we close this workflow we add the Implementation process as well. Ready for Implementation indicate that the requirement process has led to a decision to implement and In Implementation indicate that the need is being fulfilled. We do not fracture this further as we can easily drill down to individual tasks in Advanced Roadmaps, and it is not really useful to have for example test and release part of this workflow. That is because each issue type will have many issue types below it, and you can only transition on the last sub-task, making it misleading and feeling stagnant.

Finally, we add a status for Blocked/Pending to allow us to track when things are preventing this activity from being fulfilled. This can be external or internal dependencies or financial reasons for example.

As always we go for an open workflow to allow for free transitions. We add a close screen to the Close status to set a resolution and then add a post function to remove resolution on all other statuses. This workflow should now look like this:

Screenshot 2021-01-05 at 18.58.09.png

The final step is now to go to our workflow scheme and add this new workflow. We do this by going to Issues -> Workflow Schemes and click edit on the workflows scheme we have Initiative, Capability and Feature added to. We click add Workflow and add the new workflow we just created. Then we select that this workflow will be applied to Initiative, Capability and Feature before hitting save.

This should now allow you to work inside Advanced Roadmaps using Initiatives, Capabilities and Features in a proper portfolio management process that allow for larger projects and programs as well as manage smaller feature or even user stories.

I hope you found this useful and as always, if you have any questions just write a comment and I will do my best to help you.


View full blog article

Link to post
Share on other sites
  • Replies 0
  • Created
  • Last Reply

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Days

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Similar Content

    • By Jimi Wikman
      Atlassian Cloud
      Your cloud-hosted products are supported by the Atlassian Cloud platform. This section usually includes changes related to multiple Atlassian Cloud products, site administration, and user management.
      Email users with suggested account changes
      ROLLING OUT From the Change details button, you can suggest that a user changes their account details to make their profile more consistent and easier to identify. Read more about administering Atlassian accounts.
       
      Give your users a Trusted permission
      ROLLING OUT From a user's Permission options, select Trusted to give certain users more responsibility. These users will be able to install and configure new products on your site and invite new users themselves.
       
      Claim accounts after verifying a domain
      ROLLING OUT To start managing accounts on your domain, we’ve included an additional step that requires you to claim accounts after verifying that you own the domain. From the table on the Domains page, click Claim accounts next to the verified domain. Read more about verifying a domain.
       
      Jira platform
      Changes in this section usually apply to all Jira products. We'll tell you in the change description if something is only for a specific Jira product.
      New user profile cards
      ROLLING OUT When you hover over someone’s name in directories, on dashboards, and in user picker fields, you’ll now start to see rich profile cards with more information and a link to the user’s profile (if you have permission to see it).
       
      New issue view: Rich user profile cards
      ROLLING OUT Get to know your team even faster. Our new user profile card provides more user information and a link to the user’s profile (if you have permission to see it). You’ll see it when you hover over someone’s name in user-picker fields (assignee, reporter, and other custom fields) and in issue activity feeds (comments, history, and the work log).
       
      Jira Software
      We're rolling out a new type of project known as next-gen. By default, any Jira Software licensed user can create their own next-gen project. These projects don't affect existing Jira projects, shared configurations, or your schemes. You can manage who's allowed to create next-gen projects with the new Create independent projects global permission. Read more about next-gen projects.
       
      New issue view for Jira Software
      ROLLING OUT Get a consistent view and edit experience with our new issue view for Jira Software. Click an issue to see its details, edit any field with a click, and add content with the quick-add buttons (under the issue summary). Take a look at the documentation for more info.
      We're adding new features and refining the design all the time, so click Give feedback on the issue view to let us know what you think.
       
      GitHub app on the Atlassian Marketplace
      ROLLING OUT We've partnered with GitHub to build a new and improved integration, which you can install at the Atlassian Marketplace. This replaces the DVCS connector in Jira's system settings. Current GitHub integrations set up under the old method will continue to work, but new integrations must be set up using the app on the Atlassian Marketplace. We're rolling out this update gradually, so it may not be on your Jira Cloud site yet.
      This won't affect GitHub Enterprise integrations, which must still be set up via the DVCS connector.
       
      Jira Service Desk
      Issues with the customer organizations field now use the organization name instead of ID when exporting to CSV
      ROLLING OUT NEW THIS WEEK When exporting Jira issues to CSV from the Jira Issue Navigator, the Custom field (Organizations) now contains the name of the organizations linked to the issue. The field previously contained the organization ID, which was not valuable for exports used for reporting.
      As part of this change, a CSV import can now match organizations by both their ID and their name. No changes are needed if you use CSV export files for import.
       
      Maintenance complete on the Request and Approvals pages
      ROLLING OUT NEW THIS WEEK We've completed some maintenance to the customer portal, you may notice some cosmetic updates to the Request and Approvals pages.
       
      New issue view for Jira Service Desk
      ROLLING OUT The new issue view groups key actions and information in a logical way, making it easier for you to scan and update requests. Learn more about the new issue view.
      Use keyboard shortcuts in your queues
       
      ROLLING OUT
      Use keyboard shortcuts to navigate around your queues and get your work done faster. You can now move through issues, select their fields, and go to the issue view from your queues just by using your keyboard!
       
      Customer portal request details page redesign
      ROLLING OUT We have redesigned the customer portal request details page to make it easier to use. You’ll notice we have added a rich text editor, sorted the activity stream from old to new, and have moved the location of the request fields, share button, approval and comment boxes.
       
      Easier configuration for the new issue view
      ROLLING OUT If you have the new issue view, you can now easily configure how your issue view looks for each request type.
      From your service desk project, go to Project settings > Request types and you'll find the new layout for making changes.
       
      Improved interface for your customer portal settings
      ROLLING OUT We’ve given the customer portal page in your project settings a visual overhaul. Settings are under suitable headings, text sizes are aligned, and overall, the page has a cleaner interface. Don’t worry, we haven’t removed any functionality.
      To see the new design in a classic project, go to Project settings > Portal settings.
      To see the new design in a next-gen project, go to Project settings > Channels > Customer portal.
       
      Confluence
      Portfolio for Jira plan macro
      ROLLING OUT NEW THIS WEEK The Portfolio for Jira plan Confluence macro lets you embed a Portfolio for Jira Server and Data Center plan in a Confluence page. Join key stakeholders in the spaces where business goals are built and tracked, and share how work is progressing across multiple projects and teams.
       
      Blogs are getting the first round of editing improvements
      ROLLING OUT If you've ever thought 'I wish it was easier to read blogs on mobile.... or on other devices', then this change is for you. Blogs are getting fixed-width layouts to improve readability across all devices. We're making a bunch of other updates to improve editing reliability and clean up your editing experience, so some macros may be temporarily unavailable while they're under maintenance. You can read more about these changes on our docs site.
       
      Teams have arrived in Confluence retrospectives!
      ROLLING OUT Instead of having to individually add each member of your team to a retrospective, Confluence now lets you assign people to Teams, so you can bulk add everyone at once.
      Use the retrospective template to see Teams in action. You can edit Teams through the retrospective-creation process, and add or edit other attendees for each retrospective you create.
       
      We're extending editing improvements to all pages on Android
      ROLLING OUT The editing improvements we made to blogs a few months ago are coming to the rest of your Android mobile pages, too. In addition to being faster and more reliable, your new pages are also responsive, optimized for readability, and have advanced tables. Some macros are still missing as we rebuild them, but you can check the list of changes and track updates to macros on our docs site.
       
      Confluence Cloud recent pages drawer
      ROLLING OUT We’ve made it easier to get to the pages you visited or worked with most recently. A new action has been added to the global sidebar that presents you with a list of your recent pages; interaction-specific tabs help you narrow the list based on your actions, like visited, edited, or saved as draft.
       
      Share pages directly with your team
      ROLLING OUT It’s now easier to share pages with everyone on your team, all in one go. When you click Share on any page or blog post, Confluence now lets you add a team – no need to enter each person individually. Learn more
       
      Bitbucket
      Retarget stacked Pull Requests
      ROLLING OUT NEW THIS WEEK Bitbucket will retarget the dependent pull requests to the branch that you're merging into, before closing the branch of the pull request you're merging. Previously, if there were dependent pull requests, you needed to update them manually with the new target branch. You will now see a checkbox with a link to the affected pull requests that will be retargeted.
    • By Jimi Wikman
      Atlassian Cloud
      Your cloud-hosted products are supported by the Atlassian Cloud platform. This section usually includes changes related to multiple Atlassian Cloud products, site administration, and user management.
      Email users with suggested account changes
      ROLLING OUT From the Change details button, you can suggest that a user changes their account details to make their profile more consistent and easier to identify. Read more about administering Atlassian accounts.
       
      Give your users a Trusted permission
      ROLLING OUT From a user's Permission options, select Trusted to give certain users more responsibility. These users will be able to install and configure new products on your site and invite new users themselves.
       
      Claim accounts after verifying a domain
      ROLLING OUT To start managing accounts on your domain, we’ve included an additional step that requires you to claim accounts after verifying that you own the domain. From the table on the Domains page, click Claim accounts next to the verified domain. Read more about verifying a domain.
       
      Jira platform
      Changes in this section usually apply to all Jira products. We'll tell you in the change description if something is only for a specific Jira product.
      New user profile cards
      ROLLING OUT When you hover over someone’s name in directories, on dashboards, and in user picker fields, you’ll now start to see rich profile cards with more information and a link to the user’s profile (if you have permission to see it).
       
      New issue view: Rich user profile cards
      ROLLING OUT Get to know your team even faster. Our new user profile card provides more user information and a link to the user’s profile (if you have permission to see it). You’ll see it when you hover over someone’s name in user-picker fields (assignee, reporter, and other custom fields) and in issue activity feeds (comments, history, and the work log).
       
      Jira Software
      We're rolling out a new type of project known as next-gen. By default, any Jira Software licensed user can create their own next-gen project. These projects don't affect existing Jira projects, shared configurations, or your schemes. You can manage who's allowed to create next-gen projects with the new Create independent projects global permission. Read more about next-gen projects.
       
      New issue view for Jira Software
      ROLLING OUT Get a consistent view and edit experience with our new issue view for Jira Software. Click an issue to see its details, edit any field with a click, and add content with the quick-add buttons (under the issue summary). Take a look at the documentation for more info.
      We're adding new features and refining the design all the time, so click Give feedback on the issue view to let us know what you think.
       
      GitHub app on the Atlassian Marketplace
      ROLLING OUT We've partnered with GitHub to build a new and improved integration, which you can install at the Atlassian Marketplace. This replaces the DVCS connector in Jira's system settings. Current GitHub integrations set up under the old method will continue to work, but new integrations must be set up using the app on the Atlassian Marketplace. We're rolling out this update gradually, so it may not be on your Jira Cloud site yet.
      This won't affect GitHub Enterprise integrations, which must still be set up via the DVCS connector.
       
      Jira Service Desk
      Issues with the customer organizations field now use the organization name instead of ID when exporting to CSV
      ROLLING OUT NEW THIS WEEK When exporting Jira issues to CSV from the Jira Issue Navigator, the Custom field (Organizations) now contains the name of the organizations linked to the issue. The field previously contained the organization ID, which was not valuable for exports used for reporting.
      As part of this change, a CSV import can now match organizations by both their ID and their name. No changes are needed if you use CSV export files for import.
       
      Maintenance complete on the Request and Approvals pages
      ROLLING OUT NEW THIS WEEK We've completed some maintenance to the customer portal, you may notice some cosmetic updates to the Request and Approvals pages.
       
      New issue view for Jira Service Desk
      ROLLING OUT The new issue view groups key actions and information in a logical way, making it easier for you to scan and update requests. Learn more about the new issue view.
      Use keyboard shortcuts in your queues
       
      ROLLING OUT
      Use keyboard shortcuts to navigate around your queues and get your work done faster. You can now move through issues, select their fields, and go to the issue view from your queues just by using your keyboard!
       
      Customer portal request details page redesign
      ROLLING OUT We have redesigned the customer portal request details page to make it easier to use. You’ll notice we have added a rich text editor, sorted the activity stream from old to new, and have moved the location of the request fields, share button, approval and comment boxes.
       
      Easier configuration for the new issue view
      ROLLING OUT If you have the new issue view, you can now easily configure how your issue view looks for each request type.
      From your service desk project, go to Project settings > Request types and you'll find the new layout for making changes.
       
      Improved interface for your customer portal settings
      ROLLING OUT We’ve given the customer portal page in your project settings a visual overhaul. Settings are under suitable headings, text sizes are aligned, and overall, the page has a cleaner interface. Don’t worry, we haven’t removed any functionality.
      To see the new design in a classic project, go to Project settings > Portal settings.
      To see the new design in a next-gen project, go to Project settings > Channels > Customer portal.
       
      Confluence
      Portfolio for Jira plan macro
      ROLLING OUT NEW THIS WEEK The Portfolio for Jira plan Confluence macro lets you embed a Portfolio for Jira Server and Data Center plan in a Confluence page. Join key stakeholders in the spaces where business goals are built and tracked, and share how work is progressing across multiple projects and teams.
       
      Blogs are getting the first round of editing improvements
      ROLLING OUT If you've ever thought 'I wish it was easier to read blogs on mobile.... or on other devices', then this change is for you. Blogs are getting fixed-width layouts to improve readability across all devices. We're making a bunch of other updates to improve editing reliability and clean up your editing experience, so some macros may be temporarily unavailable while they're under maintenance. You can read more about these changes on our docs site.
       
      Teams have arrived in Confluence retrospectives!
      ROLLING OUT Instead of having to individually add each member of your team to a retrospective, Confluence now lets you assign people to Teams, so you can bulk add everyone at once.
      Use the retrospective template to see Teams in action. You can edit Teams through the retrospective-creation process, and add or edit other attendees for each retrospective you create.
       
      We're extending editing improvements to all pages on Android
      ROLLING OUT The editing improvements we made to blogs a few months ago are coming to the rest of your Android mobile pages, too. In addition to being faster and more reliable, your new pages are also responsive, optimized for readability, and have advanced tables. Some macros are still missing as we rebuild them, but you can check the list of changes and track updates to macros on our docs site.
       
      Confluence Cloud recent pages drawer
      ROLLING OUT We’ve made it easier to get to the pages you visited or worked with most recently. A new action has been added to the global sidebar that presents you with a list of your recent pages; interaction-specific tabs help you narrow the list based on your actions, like visited, edited, or saved as draft.
       
      Share pages directly with your team
      ROLLING OUT It’s now easier to share pages with everyone on your team, all in one go. When you click Share on any page or blog post, Confluence now lets you add a team – no need to enter each person individually. Learn more
       
      Bitbucket
      Retarget stacked Pull Requests
      ROLLING OUT NEW THIS WEEK Bitbucket will retarget the dependent pull requests to the branch that you're merging into, before closing the branch of the pull request you're merging. Previously, if there were dependent pull requests, you needed to update them manually with the new target branch. You will now see a checkbox with a link to the affected pull requests that will be retargeted.

      View full blog article
    • By Jimi Wikman
      Notion.so is a relatively new product, but it is already making some waves and is often mentioned in comparison with Atlassians products. At first glance it has a good spread of functionality and a price that can really challenge the Atlassian giant, especially for small to medium companies.
       
      "Write, plan, collaborate, and get organized. Notion is all you need — in one tool."
       
      Notion.so started in 2016 in San Fransisco and it has already attracted many users to its simple, yet powerful features. On their website they have 4 areas that they see as their core: Notes & docs, Knowledge base, Tasks & Projects and Database. If we compare these with the Atlassian suite it is pretty much Confluence with Trello baked into one product.
      The editing capabilities are not bad and Notion.so uses an inline editing function rather then the old click to edit function in Confluence. It is very nice and uses the "/" command to access the functions rather than a toolbar. The permissions system is a bit different, but seem pretty solid from what I can tell. Once you get the hang of things it is very, very easy to build content with Notion.so.
      The capabilities for Tasks & Projects are very similar to Trello so if you know how to work with Trello you should have no issues with Notion.so. If anything I feel that Notion.so actually have a more capable feature set than Trello by allowing a ton of fields that can be customized to create some pretty sophisticated setups. While not nearly as powerful as Jira for development purposes, this is is more than enough for many other situations.

      Databases follow pretty much the same capabilities as for tasks and pages. In fact tasks comes from a database by default. This means that you can create pretty awesome databases with multiple views, including tasks, lists and even a calendar view. Personally I love the feature that each row in my table can be edited as a separate page.
      At a very affordable price compared to Confluence and Jira with pretty solid features this is not a bad alternative. There are some concerns regarding security as Notion.so do not have any ISO, SOC 2, HIPAA certificates, but considering they have passed reviews from companies such as Slack and Intercom that is probably not a big thing for it's user base.
      I see Notion.so as a good alternative for small to medium non-development companies. It can work for smaller development companies as well as for large non-development companies, but I think the sweet spot is in the small to medium non-development area. The price also suggest that as it is user based and at the top tier with 20 dollars per user it is getting pretty expensive.

       
      I like Notion.so and I think it definitely have a place in some organizations. It is clearly being developed with passion where the goal is not to make money, but to make people's life easier and more organized. As always they get an extra gold star for giving students and educators this awesome product for free.
      Notion.so comes as an online cloud solution, a mobile app as well as downloads for mac and windows that even allow offline editing....and did I mention it has a dark mode that is simply amazing?
      If you have not tried it, then go and sign up for a free account today and give it a go.
       

      View full blog article
    • By Jimi Wikman
      Notion.so is a relatively new product, but it is already making some waves and is often mentioned in comparison with Atlassians products. At first glance it has a good spread of functionality and a price that can really challenge the Atlassian giant, especially for small to medium companies.
       
      "Write, plan, collaborate, and get organized. Notion is all you need — in one tool."
       
      Notion.so started in 2016 in San Fransisco and it has already attracted many users to its simple, yet powerful features. On their website they have 4 areas that they see as their core: Notes & docs, Knowledge base, Tasks & Projects and Database. If we compare these with the Atlassian suite it is pretty much Confluence with Trello baked into one product.
      The editing capabilities are not bad and Notion.so uses an inline editing function rather then the old click to edit function in Confluence. It is very nice and uses the "/" command to access the functions rather than a toolbar. The permissions system is a bit different, but seem pretty solid from what I can tell. Once you get the hang of things it is very, very easy to build content with Notion.so.
      The capabilities for Tasks & Projects are very similar to Trello so if you know how to work with Trello you should have no issues with Notion.so. If anything I feel that Notion.so actually have a more capable feature set than Trello by allowing a ton of fields that can be customized to create some pretty sophisticated setups. While not nearly as powerful as Jira for development purposes, this is is more than enough for many other situations.

      Databases follow pretty much the same capabilities as for tasks and pages. In fact tasks comes from a database by default. This means that you can create pretty awesome databases with multiple views, including tasks, lists and even a calendar view. Personally I love the feature that each row in my table can be edited as a separate page.
      At a very affordable price compared to Confluence and Jira with pretty solid features this is not a bad alternative. There are some concerns regarding security as Notion.so do not have any ISO, SOC 2, HIPAA certificates, but considering they have passed reviews from companies such as Slack and Intercom that is probably not a big thing for it's user base.
      I see Notion.so as a good alternative for small to medium non-development companies. It can work for smaller development companies as well as for large non-development companies, but I think the sweet spot is in the small to medium non-development area. The price also suggest that as it is user based and at the top tier with 20 dollars per user it is getting pretty expensive.

       
      I like Notion.so and I think it definitely have a place in some organizations. It is clearly being developed with passion where the goal is not to make money, but to make people's life easier and more organized. As always they get an extra gold star for giving students and educators this awesome product for free.
      Notion.so comes as an online cloud solution, a mobile app as well as downloads for mac and windows that even allow offline editing....and did I mention it has a dark mode that is simply amazing?
      If you have not tried it, then go and sign up for a free account today and give it a go.
       
    • By Jimi Wikman
      The Roadmap feature in Jira Cloud's NextGen projects is getting three new features. While all good additions, the question still remain who these new features are for and to what extent these new features will make people move over to NextGen projects.
      NextGen for Jira Cloud is in a strange place as it is not really defined what is can and should be used for. The Roadmap feature is in a similar place as it fall somewhere between Portfolio for Jira and the Roadmap planner macro in Confluence. These 3 new features are an improvement and a good indication on where Atlassian are going. The question is just how fast these new features are coming out and if it appeal to the target audience.
      Drill down into the details

      The first feature is the ability to open up the Epic and see the underlying tasks. This is a much needed feature that was heavily requested and also one I spoke with Atlassian about earlier this fall. This is a good feature and a good step to improve the roadmap, but is still in need of further refinement.
      We still only have Epics as the starting point, which will limit the use of Roadmaps. Opening up the subtasks will only show their status at the moment, which is useful, but not what many want. Many still want a Gant view where the sum of the subtasks should make up the time in the Epic. This is not possible at the moment and I find it interesting that Atlassian has chosen to follow an Agile first approach to the Roadmaps, which means it will not be very useful for the majority of the companies using Atlassian's products today.
       
      Add new tasks directly in the Roadmap

      Another great feature that was much requested is the ability to create new sub tasks directly in the Roadmap.  This way we can build up a full stack of tasks for a project in one view, which is excellent for portfolio and project planning purposes. The fact that we do not get full Gantt view for the sub tasks makes this a little less useful for time and resource planning however.
       
      Filter your Epics and Tasks

      The ability to use different filters is a must for any Portfolio, but even roadmaps benefit from filtering options. In this release we get the filters for issue status and assignee, which is a good start. I would like to see some more filters like dependencies and of course issues that are behind the time schedule. The question is just who this Roadmap feature is for though as then we are moving more into project management and Portfolio management and Atlassian has previously stated that the Roadmap is for teams.
       
      It's a good start, but...
      I am still not sure where NextGen projects are heading, which means it's hard to say if the features are great or poor. We know that Roadmaps will be ported over to the Classic project types as well, but that will make things even more confusing. This is unfortunately a common issue with Atlassian as they are getting more and more fractured with no clear indication on structure or strategy.
      Roadmaps for me is something that should stay as a team tool for small teams to give an overview of the current work. To cater to that need Roadmaps could benefit from a few changes.
      The first would be to change the basic structure and allow the view to be in any level. That means that I should be able to use Stories rather than Epics as Epics are just containers and not work tasks. The majority of issues are not connected to Epics in most teams, especially if you work in a Kanban setting for continuous improvements for example.
      The second would be to go full gantt, or rather to give the option to go full gantt. Not every team need or will use estimation in issues, but most do. Without a full gantt the view of issues will not be as useful as a progress overview tool. It's like saying that I have a container of a certain size and in that container I have put five items. On the question if the items will fit my only answerr will be "I don't know", which is in many organizations not an acceptable answer.
      The third would be to add dependencies on issues and not just on Epics and extend the data to also show data from other projects. In most organizations dependencies are not within the team itself, but to surrounding teams. Even if the view is for the team it makes sense that I should be able to see what other teams could be affected.
      The fourth would be to ensure that Roadmaps becomes a granular part of a larger view. Right now it is an isolated feature, which means that we will have different data for different levels of the organization. This will lead to miscommunication within the organization as teams will say Epics, which will mean something very different to Program managers and Portfolio managers and so on. As more and more organization add SAFe to their processes it is important that the team view is part of the greater whole.
      I am sure we will so many great additions to Roadmaps in 2020 and hopefully many of the questions we have regarding Roadmaps and NextGen projects will get answers then. Until then these three new features are welcome additions that I am sure will help many teams improve their work processes.

×
×
  • Create New...