Information Technology Reference
In-Depth Information
9.3.2.2.2 Project Champions.
The project champions are accountable for the
performance of Belts and the results of projects; for selection, scoping, and successful
completion of Belt projects; for removal of roadblocks for Belts within their span of
control; and for ensuring timely completion of projects. The following considerations
should be the focus of the deployment team relative to project champions as they lay
down their strategy relative to the champion role in deployment:
What does a DFSS champion need to know to be effective?
How should the champion monitor impact and progress projects?
What are the expectations from senior leadership, the Black Belt population,
and others?
How are the expectations relative to the timeline for full adoption of DFSS into
the development process?
What is the playbook (reference) for the champions?
What are the “must have” versus the “nice to have” tools (e.g., Lean DFSS
project application)?
How should the champion be used as a “change agent?”
Which failure mode and effects analysis (FMEA) exercise will the champion
complete—identifying deployment failure modes, ranking, or corrective ac-
tions? The FMEA will focus on potential failure modes in project execution.
How will the champion plan for DFSS implementation: timely deployment plan
within his or her span of control, project selection, project resources, and project
pipeline?
Will the champion develop guidelines, references, and checklists (cheat sheets)
to help him or her understand (force) compliance with software DFSS project
deliverables?
The roles and responsibilities of a champion in project execution are a vital
dimension of successful deployment that needs to be iterated in the deployment com-
munication plan. Champions should develop their teachable point of view, elevator
speech, or resonant message.
A suggested deployment structure is presented in Figure 9.1.
9.3.2.2.3 Design Owner.
This population of operative is the owner of the soft-
ware development program or software design where the DFSS project results and
conclusion will be implemented. As owner of the design entity and resources, his
or her buy-in is critical and he or she has to be engaged early on. In the Prede-
ployment phase, design owners are overwhelmed with the initiative and wondering
why a Belt was assigned to fix their design. They need to be educated, consulted on
project selection, and responsible for the implementation of project findings. They
are tasked with project gains sustainment by tracking project success metrics after
full implementation. Typically, they should serve as a team member on the project,
participate in reviews, and push the team to find permanent innovative solutions.
Search WWH ::
Custom Search