Chronological view VS Hierarchical view

[&e7]

Something I've often struggled with when managing big projects in MSP is the
battle between ordering my schedule in a heirarchical manner or a
chronological manner.

To make things easier and stop MSP making 'clever' decisions as to when
tasks happen, I always use ID only levelling. I find that gives me more
control over when things happen.
During project breakdowns, I organise my scheudle hierarcihly into software
features, and it all looks nice and neat. Of course that's not how a project
gets MADE, so I have to set the order in which they're done.

The SIMPLEST method for me is to simply move the features from the BACKLOG
into roll-ups for the month it looks beautiful and then it's nice and easy
for myself and the team to see what activities and dependencies are for the
months ahead. I can also track VERY easily if a month's work is running
behind. However, that's at the price of seeing the context of where the work
fits into the rest of the project.

What do other people do to get the best of both worlds?
I've tried tagging tasks with feature names, that's good but prone to human
error.

 

[Jim Aksel]

Try using some of the customized view and sorts.
Project/Sort.. you can sort by a number of things like start date. Or a
custom sort.
Project/Group By/Customize Group By... here you can group things the way
you want as well.

There are also other filters for date ranges, start dates, etc.

See if any of that helps
--
If this post was helpful, please consider rating it.

Jim Aksel, MVP

Check out my blog for more information:
http://www.msprojectblog.com