programmechangemgt
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| programmechangemgt [2021/10/26 17:08] – suhaw | programmechangemgt [2021/11/02 02:17] (current) – 218.212.182.200 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Programme and Change Management ====== | ====== Programme and Change Management ====== | ||
| + | |||
| + | |||
| + | |||
| + | ===== Tuesday 2 November 2021 ===== | ||
| + | |||
| + | ==== Katie Rice ==== | ||
| + | |||
| + | === Behavourial Nudges === | ||
| + | |||
| + | Types of nudges | ||
| + | * Anchoring | ||
| + | * Framing | ||
| + | * Goal setting | ||
| + | * Identity priming | ||
| + | * Defaults | ||
| + | * Rules of thumb | ||
| + | * Commitment devices | ||
| + | * Active Choice | ||
| + | * Social: peer pressure | ||
| + | * Public commitment | ||
| + | * Group incentives | ||
| + | * Social proof | ||
| + | * Social norms | ||
| + | * Competition | ||
| + | * Reinforcement | ||
| + | * Reminder | ||
| + | * Feedback | ||
| + | * Micro incentives | ||
| + | * Reduce Hassles | ||
| + | * Planning prompts | ||
| + | * Deliberative friction: Brings to attention the difficulties that will arise | ||
| + | * Salience | ||
| + | * Next step checklist: makes it easier | ||
| + | |||
| + | Resources: | ||
| + | * Richard Thaler | ||
| + | * Daniel Kahneman | ||
| + | * Dan Ariely | ||
| + | * Charles Duhigg | ||
| + | * Robert Cialdani | ||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | ===== Wednesday 27 October 2021 ===== | ||
| + | |||
| + | ==== Mukund ==== | ||
| + | |||
| + | === Change Management Tools === | ||
| + | |||
| + | https:// | ||
| + | |||
| + | Project Management tools | ||
| + | * Atlassian | ||
| + | * Jiro | ||
| + | * Confluence | ||
| + | * Trello (cards based) | ||
| + | * PLanView | ||
| + | * Resource allocation/ | ||
| + | * MS Project | ||
| + | * Workflow, swim lanes | ||
| + | * GANTT chart for critical path analysis | ||
| + | * BCG Key | ||
| + | |||
| + | Shows up reports, dependencies, | ||
| + | |||
| + | |||
| + | Leadership behaviour change | ||
| + | * BCG Amethyst | ||
| + | * https:// | ||
| + | * Power of Habits ? | ||
| + | |||
| + | Change Load Assessment | ||
| + | * BCG Absorb | ||
| + | * https:// | ||
| + | |||
| + | |||
| + | |||
| Line 6: | Line 85: | ||
| ==== Mukund ==== | ==== Mukund ==== | ||
| - | === Change Communication Plan=== | + | === Change Communication Plan === |
| * Who: Stakeholder | * Who: Stakeholder | ||
| Line 281: | Line 360: | ||
| Waterfall is outcome oriented; Agile is output oriented | Waterfall is outcome oriented; Agile is output oriented | ||
| - | How likely is a project to succeed? DICE = D + 2I + 2C1 + C2 + E | + | How likely is a project to succeed? |
| * Duration | * Duration | ||
| * Integrity: Performance of team, staff adequacy, willingness/ | * Integrity: Performance of team, staff adequacy, willingness/ | ||
| Line 298: | Line 377: | ||
| * Milestones | * Milestones | ||
| - | Milestones should be CATT: Clear, Aggregated, Tangible, Timely | + | Milestones should be **CATT: Clear, Aggregated, Tangible, Timely** |
| * Clear: Major achievement are concise | * Clear: Major achievement are concise | ||
| * Aggregated: appropriate level of granularity | * Aggregated: appropriate level of granularity | ||
| Line 304: | Line 383: | ||
| * Timely: regularity of activity | * Timely: regularity of activity | ||
| - | Rigour Testing are used to evaluate project prior to their launch: | + | **Rigour Testing** are used to evaluate project prior to their launch: |
| * Roadmap clearly defined ? | * Roadmap clearly defined ? | ||
| * Clear owner of Roadmap | * Clear owner of Roadmap | ||
| Line 321: | Line 400: | ||
| * Critical interdependencies exposed and tested | * Critical interdependencies exposed and tested | ||
| * Explicit and regular review milestones for the Roadmap; sufficient to enable effective program and senior mgmt. overview of key issues/ | * Explicit and regular review milestones for the Roadmap; sufficient to enable effective program and senior mgmt. overview of key issues/ | ||
| + | |||
| + | What makes a PMO effective ? | ||
| + | * Clear targets | ||
| + | * Reasonable targets | ||
| + | * Milestone CATT | ||
| + | * DICE: sanity check, pre-empt challenges | ||
| + | * Robust Rigour Testing | ||
| PMO role descriptions (High-level) | PMO role descriptions (High-level) | ||
| Line 360: | Line 446: | ||
| 3 distinct journeys for digital transformation | 3 distinct journeys for digital transformation | ||
| - | * Programme: Track, increase transparency, | + | |
| - | * Leader: hardwire change and inspire workforce | + | |
| - | * People: involve employees, prepare and train for change | + | |
| + | |||
| + | Principles of PMO: | ||
| + | * Transparency, | ||
| + | * Timely | ||
| + | * Impact oriented | ||
| + | * Disciplined | ||
| Programme execution 6 steps: | Programme execution 6 steps: | ||
| Line 369: | Line 461: | ||
| * Define clear accountabilities at all levels | * Define clear accountabilities at all levels | ||
| * Establish robust review cadence | * Establish robust review cadence | ||
| + | * fortnightly SteerCo reporting/ | ||
| * Escalate issues and manage risks tightly | * Escalate issues and manage risks tightly | ||
| * Track success factors and benefits | * Track success factors and benefits | ||
programmechangemgt.1635268101.txt.gz · Last modified: 2021/10/26 17:08 by suhaw