2

If I have epics that are not broken up into stories yet, how do I add them in the release burn down chart If you want to do a release burn down that includes the epics then you will need to estimate the number of story points in the epic. It is up to you and the team to decide how much effort you will put in to this. For example, the team could take a look ...


2

I believe some project management software which supports burndown charts can help you. As I'm working as a support specialist for Eylean Board I can answer your question in the context of our software. For instance, in Eylean you can have two or more levels of tasks (based on a parent-child hierarchy principle). You can use parent tasks as epics and child ...


2

I would recommend looking up the GO (goal orientated) roadmap by Roman Pilcher. He makes the template available as a free download. Your choice in tool is unlikely to help you building a better road map. Often roadmaps go into too much details (specific tasks) rather than keeping the planning at a strategic level. This is a common problem across many teams. ...


2

Product Owner role in Scrum is meant to handle conflicting priorities You said: ...causing the devteam to receive last-minute requests from some managers. Traditional approaches, such as waterfall, assumed that requirements can be written down at the beginning of the project and any changes to that handled through a change management process. Agile ...


2

Similar experience here, and I finally decided to maintain two documents: One Micro plan using gantt to schedule tasks for the next week (so reviewed weekly) One Macro roadmap with a simple spreadsheet document in order to have an overview of the release on a monthly/quarterly basis of each modules, which looks like this:


1

The Vision is the expected end state, especially as it pertains to the business/user/customer facing end state. Simple example: Umbrella or similar product Vision: when walking outside I will be, using a light-weight, easily portable device, protected from sun, rain, wind. Proposal will describe what product or service the contracting organization will ...


1

I surmise that what you're calling a "spontaneous task" is when a trouble-ticket is filed that has to be dealt with right away. These activities are separate from the project that you're roadmapping, and don't belong in it. But you do need to record and account for the time. You do need to know what percentage of your work-day is available for ...


1

As pointed out by other answers, a roadmap and making a plan are different in concept. In practice, however the two often mix. A roadmap is a big picture of your product strategy or direction. It lays out the things that need to come together to build an useful project and meet your goals. If you think about the roadmap as a plan, then it's the high level ...


1

As you say, your overall goal is to have an overview of the work being done, which would be visualized in the bigger time span, as opposed to our week to week work where we focus on smaller tasks at a time In that case... why not just have a catch-all 'Spontaneous' Epic to which you assign all such spontaneous Tasks? The reason why I wouldn't use a catch ...


1

There is a difference between a roadmap and planning. It seems to me that you try to plan all the work so that the PO knows when it is done and thus omit work to an epic eventhough it belongs there. That looks wrong to me. A roadmap, in my eyes, shows the priority of things you want to work on but has no deadlines. The team (to be clear: all roles in the ...


1

Does this project have any 'business' behind it? I only see mentions of technical stuff, but there's always business (of some kind) behind. So I see the lack of 'functional' artifacts in this list. Follow my comments inline: 1- story map. It must be seen as paramount to keep the traceability between business requirements and the stories, into which the ...


1

The essence of Agile is to do barely sufficient documentation so that you can get going and learn more. For your immediate purposes, you need the process flow/functionality for the classical windows app so draw this first. If you think there may be specifics that are different for the mobile flow, you can add this as you find them later on, or even add them ...


1

I have found story maps are a useful way to help prioritise a team's work. The map allows you to categorise what is in each release and so order your product backlog. As such, I would suggest that combining both solutions on one map might be the better approach. If you do two separate maps then you will have to figure out how to prioritise across them. For ...


1

This can be confusing because there is no authoritative body that sets terminology for Agile and, therefor, there is not "right" answer. But, these definitions and distinctions should be close. Roadmap The roadmap provides stakeholders with a view of how the product might roll out. Many teams do a planning that is longer out than a sprint but within about ...


1

If scope amount is not very different from month to month, then maybe you should just have some cross-functional team with average or higher-than-average capacity needed. If scope of critical tasks for a month is small, then they can work on low-priority fixes -- there is always plenty of such tasks in every product. If scope amount is very different every ...


Only top voted, non community-wiki answers of a minimum length are eligible