The theme for this month is Project Management! Here are three great PM-themed article submissions from a few of our seasoned Project Managers. Whether you are a Project Manager or not, everyone can benefit from these useful and practical management tips. Learn why Excel doesn't exactly excel as a project management tool, see the 4 project management skills that everybody needs to know, and review this guide to tracking percent complete throughout a project.
Source: Workzone Blog
Takeaway: Reading “just throw it in Excel” hit too close to home. Too many times over the years clients have tried to manage their part of a project in Excel rather than in our, or at least their, project management software. It’s easy, or we already have it are often among the responses. Inevitably, to of my favorite (yet also dreaded) sayings, inevitably follow: “bad data is worse than no data,” and “the cheapest solution is not always the least expensive.” Trading Excel files back and forth almost always leads to information that requires time-consuming consolidation and deduplication. The time spent when projects go well despite Excel, let alone the cost of delayed projects, typically eats away any (and more) of the savings of using Excel. Among the “7 Reasons Why Excel Doesn’t Work For Project Management” enumerated in the article, “Limited Insights = More Mistakes,” “Project details can get lost in Excel,” and “Confusion is the norm” really resonated with me. This is why we dumped Excel as our primary management tool over ten years ago. We currently use Projects from Teamwork.com for our project management, though are many tools from free to dear that do a far more competent job than Excel.
Takeaway: "Even if you are not a project manager, nearly everyone will be involved in projects in their career and personal life. While there are many aspects of project management that are valuable for everyone, some less obvious ones are:
- Agreeing on what will get done, how, for whom, and what will mean success
- Determining whether a project should happen before it starts
- Analyzing project risk
- Post project debriefs of what went well and what could be improved upon
Takeaway: The author discusses three separate methods of tracking percentage completion of tasks (and projects).
- Using professional judgment, whether your own or that of your SMEs. This is potentially the best when your judgment or that of your SMEs is accurate and generally available.
- Weighted activities can be used to measure percent completion. The concept is that if your task can be measured into discrete chunks, you can measure progress based on that. For instance, 500 lines of code can be broken into 5 100 line chunks, each of which is 20%. This is straightforward and therefore relatively easy to track, but it assumes that each section is the same level of effort, which may not be accurate.
- If a task is difficult to judge (or if you and/or your SMEs have relatively little experience with this type of task) and it doesn't break down well into parts, you can use arbitrary numbers to measure percentage. The example used is 0% for tasks that haven't been started, 20% for started, and 100% for complete. This can be an easy way to measure something about a task, and may be necessary if you are getting poor estimates or no estimates from your team, but it lacks the benefit of precision compared to the other options.
Ultimately, measuring the percentage of completion is a helpful way to keep an eye on overall project progress; depending on the nature of the tasks in your project, you may find one or more of these options helpful.
Messy web project? Our Project Managers can help streamline your development efforts.