- Avoided business-continuity[efn_note]Plans to deal with major disruption[/efn_note] threats:
- captured and terminated unapproved, informal change.
- Caught unapproved change and dismissed vague Requests for Change:
- defended change governance.
- Collated rejected change proposal information:
- advised why exception or reassessment is needed.
- Coordinated regular non-Agile (freeze-unfreeze-freeze) releases:
- safeguarded business-as-usual.
- Directed Change[efn_note]Standards and procedures for efficiently handling tool, system, standard and procedure change[/efn_note] and Release[efn_note]Standards and procedures to protect the integrity of changed tools, systems, standards and procedures[/efn_note] Management:
- maintained business continuity through Change Control[efn_note]Controlling organisational change[/efn_note].
- Directed operations handover to department and team:
- defined post go-live or early-life support.
- Facilitated effective, lasting change:
- developed cross-function workflows for non-Agile project change.
- Formalised Transition Management:
- received non-Agile output from waterfall[efn_note]Linear, sequential project approach[/efn_note] project-delivery chaos.
- Maintained systems-thinking[efn_note]A belief that components act differently when isolated from a system or other components, and that components react when other components change within a system[/efn_note]:
- understood how elements operate, interact and influence each other.
- Mandated testing, regression testing and remediation planning[efn_note]A back-out plan for restoring initial situations after failed change[/efn_note]:
- flagged deficient change prerequisites.
- Prevented policy violations or data security breaches:
- developed release and transition[efn_note]Build and deploy solutions into business use[/efn_note] best practices.
- Refined cross-functional Request for Change[efn_note]Requesting formal implementation of change[/efn_note] procedures:
- enforced DTAP[efn_note]An architecture for building and deploying solutions: development, testing, acceptance and production[/efn_note] and proofs-of-concept[efn_note]Demonstrating ideas’ feasibility[/efn_note].
- Sat on a Change Advisory Board[efn_note]Assess, advise and prioritise on requested change[/efn_note]:
- assessed, approved, rejected or deferred Requests for Change.
- (Also see Words and Literacy)
The home of Matsuda Mulville Thinking