An organization may choose to approach process improvement from either the Process area capability improvement approach Organizational maturity improvement approach CMMI models support each approach with a representation.
Software Engineering is not considered an engineering discipline throughout the world when compared to electrical engineering, mechanical engineering, and civil engineering. Software Engineeringâ€™s brief history has been filled with problems: Cost overruns Schedule slippage Poor performance compared to specification Unsatisfied customers
What youâ€™ll see: Unclear who is authorized to make what decisions? Decisions are made on primarily subjective basis Same issue is â€œdecidedâ€ over and over and overâ€¦â€¦ Rationale for earlier decisions is unavailable when needed to understand the decision later in the project Only a few choices considered for major…
July 7, 2009
What youâ€™ll see: Idealistic approach that assumes â€œall is wellâ€ even when there is evidence that all is NOT well Issues that are known risks to project staff are a surprise to management Every time a new problem manifests, a new management technique is tried
What youll see: Staff attending training courses they dont need Staff avoiding training that is provided Inappropriately-skilled staff being assigned to tasks, often without knowledge of the deficiency Staff arent released to attend training they do need.
Definition isnâ€™t done wellâ€¦.. What youâ€™ll see: Staff resists using the guidance in the standard processes that have been defined Mother of all process manualsâ€ sits on the real (or virtual!) shelf Lots of time being spent getting process waivers Extreme amount of tailoring requested by each project.
What youâ€™ll see: Lots of staff changes in the Engineering Process Group or equivalent Lack of visible senior management support for process improvement activities The things that are chosen for improvement are not aligned with business priorities False starts and rocky implementations of improvement efforts.
What youâ€™ll see: Lots of user change requests before/soon after the product is released Arguments among the technical staff as to what the user â€œreallyâ€ wants Released product doesnâ€™t meet user expectations.
What youâ€™ll see: Disagreement among technical staff as to the â€œdone-nessâ€ of different components Product under test doesnâ€™t meet requirements/design expectations Defects that could have been caught early escape into later life cycle phases due to that Increase in integration/test time.
What you’ll see: Subsystems don’t operate together Increased integration/test time Building test harnesses/procedures/etc late in the project Integration environment is inadequate to support the integration activities.
Rajendra Khare (MD)
DQS Certification India Private Limited
USA Phone: 703-574-4929, 703-574-4962
Rajendra's LinkedIn Profile
Rajendra is a qualified and certified Lead Appraiser and Instructor for the following :