Comments for Aavssitedev’s BlogProject and stakeholder management topicsSun, 03 Mar 2024 04:47:38 +0000hourly1http://wordpress.com/Comment on The major news story everyone missed: KPMG hit with record fine for their role in the Carillion Collapse. by Ethics and Governance in Action | Mosaicproject's Blog/2023/10/24/the-major-news-story-everyone-missed-kpmg-hit-with-record-fine-for-their-role-in-the-carillion-collapse/#comment-8822Sun, 03 Mar 2024 04:47:38 +0000/?p=4431#comment-8822[…] a lot of commentary on major ethical failures by some of the ‘big 4’ accountancy firms (see: The major news story everyone missed: KPMG hit with record fine for their role in the Carillion Coll…). With a common theme being attempts by the partners running these organizations to minimize their […]

]]>
Comment on A Brief History of Agile by bgbgbgbg/2024/02/03/a-brief-history-of-agile/#comment-8821Sun, 04 Feb 2024 20:26:07 +0000/?p=4632#comment-8821Thank you for this concise connection between Waterfall and Agile. It was a missing piece (one of many) in my understanding of these methods. bgbg

]]>
Comment on DCMA 14 Point Schedule Assessment – Updated by drpdg/2023/07/01/dcma-14-point-schedule-assessment-updated/#comment-8820Mon, 29 Jan 2024 11:42:44 +0000/?p=4348#comment-8820PS, FWIW, in a lengthy debate with Vladimir Liberzon (VP of Spider Software) on Linked In a couple of years back, he finally admitted that he does the same thing we do, which is to use Rolling Wave Planning (Sprints or Scrums by our IT colleagues) and he does exactly what we’ve been advocating for well over 50 years, which we have been treating all projects as being RESOURCE CONSTRAINED and well over 80% of the activities in our CPM schedules utilize PREFERENTIAL or “Soft” logic. Why? Because no project EVER has exactly the optimum size or exactly the optimum number of equipment and as most contractors utilize a mix of their own people and subcontractors, very rarely can you achieve the OPTIMUM mix of trades (by ratios or by numbers) And as we were a Union Contractor, if we needed more tradespeople, all we had to do is call the hall and if they were short, they would call the adjacent locals. (We did a lot of offshore oil platforms and because platforms are considered ships and you can only put so many people on the ship at the same time, you cannot begin to imagine how we have to jump through the hoops to “balance” the composition of the different trades, often on a shift-by-shift adjustments.)

Bottom line. There are precious few planners/schedulers who have that depth of field experience, which explains the TRUTH about why so many projects run LATE and/or OVER BUDGET. https://pmworldlibrary.net/wp-content/uploads/2023/09/pmwj133-Sep2023-Giammalvo-futility-of-master-plans-prepared-with-little-or-no-hands-on-experience.pdf

]]>
Comment on DCMA 14 Point Schedule Assessment – Updated by drpdg/2023/07/01/dcma-14-point-schedule-assessment-updated/#comment-8819Sat, 27 Jan 2024 11:15:27 +0000/?p=4348#comment-8819Pat and Alex,
Keep in mind that under the requirements from the DAU and DCMA, their primary focus is on AUDITING- designed to “catch” contractors if they have or are in the process of cheating the US Government. (See Abba, Wayne (2023) “It’s Time to “Reboot” Earned Value Management” Defense Acquisition University Blog
https://www.dau.edu/library/defense-atl/blog/Reboot-Earned-Value-Management and Reynolds, Chad (2023)
https://www.dau.edu/library/defenseatl/blog/PlanningfortheFutureofEarnedValueManagement

When I was actively involved with the GAO as an “independent consultant” when compiling BOTH the Cost and Scheduling “best tested and PROVEN” practices, those of us contributing from the roles of CONTRACTORS are not looking at the schedule for AUDITING but as FORECASTING- as a RESOURCE ALLOCATION/MANAGEMENT TOOL and to serve as DEFENSIVE (or OFFENSIVE) purpose to protect us against claims and help to perfect or substantiate our claims against the OWNERS DELAYS and CHANGE ORDERS. VERY DIFFERENT from how the NDIA and private sector contractors need or use the CPM schedule. https://pmworldlibrary.net/wp-content/uploads/2023/09/pmwj133-Sep2023-Giammalvo-futility-of-master-plans-prepared-with-little-or-no-hands-on-experience.pdf

And IF the CPM schedule has NOTHING to do with EVM, then why do they bother with SV or SPI? Or the false and misleading claims by PMI and Walt Lipske with their claims about “Earned Schedule”? Wayne Abba and I have agreed since PMI and Lipske made that claim both Wayne and I agreed that “Earned Time” and “Earned Schedule” have always dated back to the ORIGINS of Earned Value, from the Industrial Revolution, which we still see in use today in shoes and clothing (and nearly all other factories, as well as “job shops” like Doctors, Dentists, Lawyers, Auto mechanics, Barbers, Hair Dressers, Engineers and anyone else who offers their services on a “walk-in” basis that is sold on a “Unit Completed” basis) in the form of what is known as “piecework.” https://pmworldlibrary.net/wp-content/uploads/2022/09/pmwj121-Sep2022-Giammalvo-origins-and-history-of-evm-a-contractors-perspective.pdf

]]>
Comment on The evolution of the DCMA 14 Point Schedule Assessment by DCMA 14 Point Schedule Assessment – Updated | Mosaicproject's Blog/2024/01/27/the-evolution-of-the-dcma-14-point-schedule-assessment/#comment-8818Sat, 27 Jan 2024 08:58:20 +0000/?p=4620#comment-8818[…] and they did change in the years before 2012 (for more on the evolution of the DCMA 14 Points see: The evolution of the DCMA 14 Point Schedule Assessment). This leads to two significant […]

]]>
Comment on DCMA 14 Point Schedule Assessment – Updated by The evolution of the DCMA 14 Point Schedule Assessment | Mosaicproject's Blog/2023/07/01/dcma-14-point-schedule-assessment-updated/#comment-8817Sat, 27 Jan 2024 08:30:24 +0000/?p=4348#comment-8817[…] The objectives of the DCMA 14 Point assessment is frequently misunderstood, this was discussed in DCMA 14 Point Schedule Assessment – Updated. […]

]]>
Comment on The Problem with Waterfall by DoubleDuce/2024/01/14/the-problem-with-waterfall/#comment-8816Thu, 25 Jan 2024 20:39:06 +0000/?p=4568#comment-8816In reply to Pat Weaver.

That Plan is called the Integrtaed Master Plan (IMP)
The IMP is part of the proposal, with its
– Program Event
– Significant Accomplishments
– Accomplish Criteria

With the IMP, the Integrated Master Schedule can be developed, and placed on baseline to be reviewed at the Integrated Baseline Review (IBR). The Tasks and their Work Packages in the IMS, feed the Accomplishment Criteria. These items can follow several topologies, Iterative and Incremental is the common one for software intensive systems in our domain. But the structure of the IMS changes are the program proceeds dependent on the changes tot eh baseline as the program proceeds, through the Change control process during execution.
But the IMP and it’s SAs and ACs requires a contract change, since those are the basis of progress payments from the contract.

]]>
Comment on The Problem with Waterfall by DoubleDuce/2024/01/14/the-problem-with-waterfall/#comment-8812Mon, 22 Jan 2024 04:59:17 +0000/?p=4568#comment-8812In reply to Pat Weaver.

2167A installs rhe Integrated Master Plan, just a 2167 did.
Yes the “fully detailed plan” is on Baseline as part of the contract award. The detailed sequence of work is also on baseline starting with the propose and cannot be changed without a Contractural Baseline Change process.
This is contractual process of DoD acquisition. It may not be your domains process, but it is our.
Any changes are made through the formal Change Control process.
But since the IMP is NOT the schedule, the actual structure of the work processes are not defined in 2167.
Figure 1 in 2167A is NOT a schedule it is a PLAN, defined by the Program Events – this are NOT milestones. The Program Events (PEs) SRR, SDR, … PDR, CDR, TRR not milestones,
Program events as described in the IMP-IMS Step-by-Step guide I sent before and restated here with a DoD Logo https://tinyurl.com/yk3zlq8c

]]>
Comment on The Problem with Waterfall by Pat Weaver/2024/01/14/the-problem-with-waterfall/#comment-8811Mon, 22 Jan 2024 00:27:03 +0000/?p=4568#comment-88112167 was based on an iterative approach.
2167A mentions ‘iterative’, but requires a complete fully detailed plan that cannot be changed before work starts and specifies in detail the sequence of development – ‘waterfall’ in all but name.

]]>
Comment on The Problem with Waterfall by Pat Weaver/2024/01/14/the-problem-with-waterfall/#comment-8810Mon, 22 Jan 2024 00:20:59 +0000/?p=4568#comment-8810In reply to DoubleDuce.

2167A (1988) replaces 2167 (1985) which was an iterative standard. While 2167A (1988) states any method can be used, it explicitly requires a fully detailed plan to be prepared before work starts and specifies the testing sequence – waterfall in all but name.
2167A was replaced by MIL-STD-498 in 1994 which was more amenable to iterative developments.

]]>