It Was An Itsy Bitsy, Teeny Weeny......
I have been managing small projects for some time now. Some of my project are really tiny, I'm talking about 8 hours of work max. Others can be 2 week or month-long projects. Some span several months, and then you get up into the 6 month and year plus undertakings.
Are You A Master?
The article is mostly based off a study done by Gartner Inc., in Stamford CT, USA. One sad but true statistic stated that 20-30% of IT executives "have a 'dismissive attitude' toward project management". Those are the same execs that suffer "from poor quality, late delivery and unrealistic project costs." I can related to this information from my personal experience, and would venture a guess that when you move into executives in operational areas, the dismissive attitude towards proper project management increases. The majority of IT execs seem to have seen the light and made the realization that there really is value to be delivered by well run projects by individuals who have the right skills to do so in a formal manner.
Avoiding Hindsight Management
So, what about knowledge
In today's world, knowledge is the asset many organizations started to recognize as being the most important aspect for creating a competitive edge in a highly volatile business environment.
Refraining from buzz words and terminology often used by management and research, knowledge is the accumulation of thoughts and skills that give a person or an organization its ability to survive, compete and prosper in the this changing and challenging world.
Work by many researchers like Nonaka in his book 'The Knowledge Creating Company' and many other researchers worldwide, has given a new dimension for knowledge management in organizations.
The research went into the details of human interaction which generates and promotes the dessimination of knowledge. Unlike manothers who advocate an Information Technology infracstructure as being the fundamental core of a knowledge system, Nonaka thinks that it more a human issue and culture than mere computers and databases.
How to Really Fix a Failing Project
Your project is in trouble. You know it. Your team knows it. But somehow you have been able to keep it from your management. You need a quick fix. But there aren’t any. What can be done to get back on track? Since yesterday's ideas didn't help, here are some suggestions that might point you in the right direction.
9 Benefits of a Project Schedule
A Quick thought on leadership
Risk Monitor & Control
Performance Reporting
PERFORMANCE REPORTING
Performance reporting involves six things:
- Status reports How’s the project right now?
- Progress reports How complete is the project? How much more work remains?
- Forecasting Will this project end on schedule? Will the project be on budget? How much longer will this project take? And how much more money will this project need to finish?
- Scope How is the project meeting the project scope?
- Quality What are the results of quality audit, testing, and analysis?
- Risks What risks have come into the project and what has been their affect on the project?
The goal of performance reporting - The purpose of reporting is to share information regarding the project performance with the appropriate stakeholders. Performance reporting is done on a regular schedule.
- Performance reports - These are the results and summation of the project performance analysis. The Communications Management Plan will detail the type of report needed based on the conditions within the project, the timing of the communication, and the demands of the project stakeholder.
- Change requests - Results of performance may prompt change requests to some area of the project. The change requests should flow into the change control system for consideration and approval or denial.
Forecasts - Have a basic understanding of Forecasts. Forecasts are updated and reissued based on work performance information provided as the project is executed. This information is about the project’s past performance that could impact the project in the future, for example, estimate at completion and estimate to complete.
Communicating change - Performance reports and change requests are an input to the following Change Control Processes:
- Integrated Change Control
- Scope Change Control
- Schedule Change Control
- Cost Change Control
Note: The project plan is one of the key inputs to performance reporting. The project plan contains the WBS, the project scope and requirements, and other documentation that can be used to measure project progress and performance. Other inputs to performance reporting are the work results. Work results can be examined and measured for quality, time spent completing the work, and the monies required to complete the work results. The work results, as progress reports or completion of work results, can be measured against the estimates and expectations to reveal variances. The Communications Management Plan will detail how values are measured, for example EVM, and at what point variances call for communications to the appropriate stakeholders. The last inputs to performance reporting are other project records, such as memos, product description, and other information relevant to the project. For example, a customer may request project status updates every quarter, regardless of where the project is in its timeline. Or a project may have multiple vendors whose contracts require differing levels and types of reporting from the project staff. This is a communication requirement that would be in the Communications Management Plan.
Information Distribution
Information can be distributed through the following as well as other methods, according to project demands and as technology provides: