2 replaced http://pm.stackexchange.com/ with https://pm.stackexchange.com/
source | link

The same way you tackle any epic: break it down into smaller chunks.

There are many different ways to do this. For example, if your project has lots of other (legacy) systems to interact with, try to find a lower-level user story that deals with ONE legacy system. And see how implementation of that impacts the overall epic story.

Another approach is to tackle things from a stakeholder viewpoint.Another approach is to tackle things from a stakeholder viewpoint.

Check out this post for yet another way to deal with it.

The same way you tackle any epic: break it down into smaller chunks.

There are many different ways to do this. For example, if your project has lots of other (legacy) systems to interact with, try to find a lower-level user story that deals with ONE legacy system. And see how implementation of that impacts the overall epic story.

Another approach is to tackle things from a stakeholder viewpoint.

Check out this post for yet another way to deal with it.

The same way you tackle any epic: break it down into smaller chunks.

There are many different ways to do this. For example, if your project has lots of other (legacy) systems to interact with, try to find a lower-level user story that deals with ONE legacy system. And see how implementation of that impacts the overall epic story.

Another approach is to tackle things from a stakeholder viewpoint.

Check out this post for yet another way to deal with it.

1
source | link

The same way you tackle any epic: break it down into smaller chunks.

There are many different ways to do this. For example, if your project has lots of other (legacy) systems to interact with, try to find a lower-level user story that deals with ONE legacy system. And see how implementation of that impacts the overall epic story.

Another approach is to tackle things from a stakeholder viewpoint.

Check out this post for yet another way to deal with it.