Skip to main content

Some General MS Project tips

I’m a self-taught MS Project user and certainly no expert, but I do know that it’s a good idea to spend the least amount of time using the tool as possible; here are some simple things that help me do that:

1. A general MS Project planning tip is to have a good old pencil and paper with you, jot down the things you are trying to do and work through them sequentially whenever you update your plan:


- Allocate next phase dev tasks

- Add dependencies

- Include new Change Request

- Add Julian's training leave

- Update % Complete on regression test

Because it’s such a fancy tool, it’s easy to become distracted, go off on tangents and forget to do basic things, so a systematic approach (I find) helps. If something occurs to you while you are say, identifying tasks, e.g. you notice a dependency crop up, then write it down on your paper and come back to it, best to finish identifying all of your tasks first.

2. When ever I start a new plan I do the following things:

  • Google for public holidays in my area and enter them as non working days
  • Enter the resources on the Resource Sheet in alphabetical order. It may sound ridiculous but it makes it faster to allocate resources using a drop down filter when they appear alphabetically. If you work in a large department you could also consider entering them in groups, e.g I prefix all of my QA resources with ‘QA’ and then organise them alphabetically.
  • Put in a start milestone for each resource under a task group I call ‘Resources Available’ , e.g. Put in a task of ‘Susan Starts’ on a fixed date and allocate Susan to it, her first task can be linked off this one. It just makes it easier to see at a glance when people start turning up, and if resources are delayed coming onto your project you can reflect the impact quickly in your plan without searching around to find their first tasks.
  • Turn Autofilters on on my Gantt View: Go to menu: Project >Filtered For : All Tasks > Autofilter.

3. Just because it’s in MS Project doesn’t make it real. I, like many project managers, have fallen foul of cooking my project plans for hours and days, attempting to get it to reflect reality, it never will. Your project is going to have many nuances, and events, and issues and changes during it’s lifecycle, if you attempt to match reality with your plan you will never do anything but maintain the plan. It’s a waste of time.

4. Don’t spend too long creating your initial plan. For most projects I would advise a maximum of three days in initial scheduling at the start of the project, collaborating with experts to identify dependencies. This will differ, I suppose, depending on how well scope is known, but really, if it’s taking longer than this then consider asking for help from an experienced scheduler.

5. When the project is in execution try to limit yourself to two hours a week in plan updates. I would usually spend an hour a week tracking during status reporting, and another hour pieced together with quick daily checks. The exception to this is when business direction changes and a re-plan is required. (Feel free to make a big deal about that so your managers know you need a re-plan exercise.)

6. Do your tracking as a ritual, on the same day every week after gathering updates from your team. If you do it ritually at the same time every week it becomes less onerous and you will get faster at it. If you make it part of status reporting then your status report updates will be easier and you’ll never be too far from knowing progress against your plan.

MS Project is a great tool for scheduling complex activities with multiple dependencies, most software projects have these characteristics, but it’s vital to get your head out of the Project Plan and go and make it happen by communicating with your team. The best way to do this is find a simple way to plan, a systematic way to track routinely and not get hung up on reflecting every little thing in the plan.

Minimise your time in the tool and Maximise your time with the team.


Văn Sát said…
Bạn là chủ xe và đang cần tìm hàng vận chuyển? Bạn là người cần tìm xe vận chuyển hàng? Vậy bạn hãy ghé vào sàn vận tải nội địa đây là nơi sẽ giúp bạn tìm thấy thứ bạn đang cần tìm. Hiện nay, chúng tôi tự hào là một trong những đơn vị cung cấp giải pháp vận chuyển hàng đầu hiện nay. Với các dịch vụ vận chuyển hàng hóa nội địa, vận chuyển Bắc Trung Nam, vận chuyển hàng đông lạnh bắc nam,... Đến với chúng tôi bạn sẽ không cần lo lắng tìm hàng hay tìm xe để vận chuyển hàng. Hiện nay thì các tuyến vận chuyển chúng tôi đang có thể kể đến như: vận chuyển hàng đi bạc liêu, vận chuyển hàng đi vũng tàu, vận chuyển hàng đi bắc ninh, vận chuyển hàng đi bến tre,... Để biết thêm thông tin hãy liên hệ với chúng tôi nhé.

Popular posts from this blog

Business Requirement Documents are just no good and should be abolished from the world of creating software

I had hoped the world could have wholeheartedly rejected Business Requirement documents by now. For too long I’ve seen the repeated scenario of only commencing the creation of a new initiative with a requirements document.Unfortunately most organisations that have teams developing software still use these flawed anathemas to creativity as the status quo. Despite agile approaches maturing and customer-centric modes of design emerging, requirements documents still persist. 
If you work in an organisation that doesn’t use business requirement documents any more, read no further. You are lucky; sense has prevailed at your place however in my experience, you are still the minority.
Let's face it; addressing this issue is not always the point you want to start your improvement work when there's much that could be dysfunctional with how a team is delivering software. But now, I find myself as mad as hell, and I'm not going to take business requirement documents anymore. I want to …

Gamify your children

Inspired by James Ross’s LAST conference talk on The Shamification of Lamification and the Reclaimification of Gamification I was motivated to try and “Gamify” the school holidays for my three children, Leo aged 8, Chloe 9 and Max 10.
Buy-in is everything, so the first thing we did was a quick workshop to extract the kids ideas. I asked them to write their ideas for good rewards on sticky notes, with a few examples for context, such as ‘trip to the movies or ‘play date with a friend’ . They had 5 minutes to come up with their ideas – one idea per sticky note (as always).
They then read out their ideas for all of us to hear, there were a few duplicates and also a few comedy suggestions. Even though we had ruled out crazy stuff, such as rewards of a million dollars, Leo had written down ‘A unicorn for the back yard’ reading it out with gleeful giggles.
Then they spent 5 minutes writing down tasks that they could do to earn rewards. By now they had the hang of it and quickly came up with t…

Agile Australia 2011 Series - Agile Governance

If you are in an industry that is heavily into governance you need some structure and process around your projects or you could find your Agile projects getting usurped by the culture of command and control. So it’s important not to shy away from the topic but to work with the entities that enforce and monitor governance. In this way you can create something that is fast and easy and not laborious to work with.I work for an Apra regulated organisation and we made keenly aware of our obligation under Apra to evidence documented change when audited. However in all organisations I’ve ever worked in, there are boundaries that bend quite a bit, ways to change things and ways to get by that satisfy governance process without crippling your agile process.There’s almost two alternating schools of thought here which are ‘work within process’ and ‘decide to change the process’. It’s actually pretty easy for my team to work within process. Project approvals, mandates and PIDs that are important …