Before addressing the question, it would be beneficial if we understand what baselining and re-baselining is. Baselining is the common project management method where we lay down the cost and effort estimates and schedules based on assumptions that we have at hand. Once baseline is created, project plan is laid out based on this baseline. But as projects go ahead, due changes in assumptions, project requirements, due to poor project oversight and other changes, the original cost / effort estimates and schedule does not fall good and calls for modification of the same based on new assumptions. If projects are not re-baselined at this stage, they fail drastically and / or lead to huge cost overrun.
Federal IT projects are not different. The situation is more obvious due to outdated (quickly changing) technology, complex systems, processes & systems, poor project estimation/planning/control mechanisms and lack of expertise to push and pull clean project management practices that leads to weak risk / change management and over and above all – politics. These situations that lead to re-baselining further determine the factors that in turn make it difficult to re-baseline federal IT projects, which include –
1. Need for re-estimation and arriving at revised cost estimation based on detailed work breakdown structureThis is one of the major factors that make re-baselining difficult task and time consuming to get on track especially when agency is dealing with multi-billion projects which are too complex to start with. Greatest concern is to make all assumptions clear and realistic so that re-baselining is avoided in future. Immediate remedial action would be to spend considerable time to figure out what the actual need is and clearly define what individual components of work / task need to be executed to achieve the task. Expert advice should be sought for each major task to determine closest cost, effort and time.
2. Need for re-work on EVM formulas and calculation to adjust new cost and valueEarned Value Management (EVM) is the most widely used and federal standard to measure performance of an IT investment. Re-baselining causes the project team / agency to rebuild EVM formulas based on new cost, effort and value and this involves considerable cost, effort and risk management to ensure that the expected ROI is attained within reasonable time period for changed scenario. Once we arrive at clear work break down structure and have a clear idea of how work / task need to be executed and integrated to achieve the clear goal, EVM analysis and establishment should not be a problem.
3. Lack of credibility on the part of agency to have this oversight and take the responsibility to fix issues and propose the business case for re-baseliningThis issue would keep the agencies from announcing the fact that they have actually overrun the budget and are in grave need to rebaseline. The memorandum from CIO and OMB director urges agencies to announce for help and declare that they need to re-baseline based on an investment’s poor performance. OMB need to ensure that it provides appropriate support for the agencies and that it gives them a chance to correct any issues that would have lead to re-baseline. OMB need to clearly define the expectations that it needs to have in a re-baseline plan and to monitor its progress.
1. usaspending.gov (2010). Federal IT Dashboard. Retrieved on 02nd November from http://it.usaspending.gov/
2. os.doc.gov (2010). US. DoC, Office of CIO – IT Investment Performance Management Policy. Retrieved on 02nd November from http://ocio.os.doc.gov/ITPolicyandPrograms/Policy___Standards/PROD01_004949
3. Whitehouse.gov (2010). Reforming the Federal Government’s Efforts to Manage Information Technology Projects. Retrieved on 02nd November from http://www.whitehouse.gov//sites/default/files/omb/assets/memoranda_2010/m_10-25.pdf
4. Whitehouse.gov (2010). Information Technology Investment Baseline Management Policy. Retrieved on 02nd November from http://www.whitehouse.gov//sites/default/files/omb/assets/memoranda_2010/m10-27.pdf
5. Whitehouse.gov (2010). Immediate Review of Financial Systems IT Projects. Retrieved on 02nd November from http://www.whitehouse.gov//sites/default/files/omb/assets/memoranda_2010/m-10-26.pdf
6. Whitehouse.gov (2010). Sharing Data While Protecting Privacy. Retrieved on 02nd November from http://www.whitehouse.gov/sites/default/files/omb/memoranda/2011/m11-02.pdf
7. Whitehouse.gov (2010). Pilot Projects for the Partnership Fund for Program Integrity Innovation. Retrieved on 02nd November from http://www.whitehouse.gov/sites/default/files/omb/memoranda/2011/m11-01.pdf