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

Okay, so here goes: This technique is called results chains and you'll at least need to have a 'list' of the strategic goals of your company - so you know what all to link to ;) Let's say you have an R&D Project 'A' say. Write down: 'implement/design/research... Project A'. Now, start by asking the question 'so-what?' - you'll get an answer. Ask 'so-...


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

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 ...


1

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 ...


1

Ken Schwaber has said that "The minimum plan necessary to start a Scrum project consists of a vision and a Product Backlog". The Product Owner is responsible for the overall product and should lead the creation of the vision. This should happen through close collaboration with the team. Conversations with stakeholders that have appropriate experience in ...


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