- Project Management understands the role change methodology, tools and deliverables play in the overall project success– check!
- We will be using agile methodology to quickly develop and migrate by business area – newer territory, but still feeling good.
- Change Management will be expected to use Jira, an agile project management tool, for the first time. We will participate in sprint planning, daily stand-ups, and retrospective “ceremonies” – let’s discuss.
We knew the hallmarks of our change methodology, tools and deliverables would still apply. But, we also knew we would need to adapt to a more iterative approach. Looking back at the work to date, we found some lessons and tips to share.
Tip #1 –Time Investments Shifted
Very early on we realized we were investing time in ways we didn’t anticipate.
- Heavy Upfront Time Investment for developing, testing and revising our communication and training toolkits with our pilot group; efficiencies were then gained with subsequent rollouts
- Frontloading Strategic Resources became necessary to support the initial CM tasks mentioned above with the ability to taper resourcing once we got into managing execution of a repeatable cadence
- Managing Change Tasks in Time-Boxed Periods or Sprints, we invested in participating in Jira through sprint planning, daily stand-ups, reviews and retrospective ceremonies. Early on this felt like an ineffective use of our time and a duplication of our planning deliverables. With time and compromise, we shaped meetings to address stakeholder relevant topics first, and we agreed to leverage Jira reports to meet components of our stage gate documentation requirements.
