The team at Eversource was familiar with agile methodology, but only a few CIS project participants had concrete experience with this implementation process. EY transformation, design and execution teams, along with Eversource’s IT Agile Center of Excellence, were brought in to quickly familiarize the broader team with agile techniques.
The team started by assessing Eversource’s agile maturity, formulating a roadmap for gradual capability enablement to deploy the new SAP functions swiftly with minimal delays. The group conducted 25 hours of Scaled Agile Framework (SAFe) training to introduce employees to the agile organization and workflow patterns intended to promote alignment, collaboration and successful delivery across Eversource’s large number of stakeholders.
To familiarize the broader team with agile capabilities, standard processes were implemented within days of the program kickoff. Daily stand-up meetings were instituted to discuss progress, risks and roadblocks as teams formulated Business Process Documents (BPDs) — the who, what, when, where and why of individual tasks. These BPDs, leveraging the EY Energy Industry Cloud for SAP solutions, would guide the relevant business areas across 10 critical workstreams, including correspondence, customer service, reporting, device management, and billing and payment.
Stand-ups were also an opportunity to introduce teams to the role of a scrum master. SAFe-certified scrum masters and coaches led the daily calls and leveraged the forum to continuously coach and upskill employees, addressing daily bubble-up topics on the fly. The work done to introduce the agile cadence and methodologies helped lay the groundwork for a more seamless transition into the design, build and test portion of the SAP CIS deployment.
Once BPDs were finalized, the entire SAP implementation shifted to a more formal SAFe agile approach. This framework is typically described using three key terms: “epics,” which are broad functional objectives spanning multiple releases; “features,” which are collections of related tasks within a single go-live release; and “stories,” which are individual tasks users will encounter daily.