Project Pain:The publisher had a project-centric view of the world. Teams were having trouble sizing work, they were struggling with story estimates and were experiencing pain with basic release planning. Dates continued to slip and QA was outside the Scrum teams. A project-centric strategy lead to unrealistic workloads. “Concepts of program and portfolio were foreign ways of thinking relative to product delivery and as a result, program and portfolio concepts were used to describe a financial milieu.”
Delivery Challenge/ Opportunity:The need to optimize their technology delivery in order to meet demand, deliver on time, keep teams motivated and excited about their work all while delivering consistent quality. “The business ultimately wants a IT Organization that consistently delivers faster, with quality and that can maintain a business-aligned economic view.” Agile was solving many of these issues but not all. Being able to manage from a program level within a well-defined portfolio structure were aspirations to the final frontier. They needed a single tool that all Agile teams could leverage. This would simplify the training standards while providing a comprehensive reporting system that encompassed all Agile teams.
SAFe Implementation:The Publisher moves to the SAFe framework and redefines value in quality, delivery and process governance. “SAFe promised a philosophy or method that allows us to assemble, prioritize and manage work within a unified portfolio and program framework.“ Soon after their first Agile Release Train, (ART), they see benefits from a program and portfolio level and can understand much of their costs in labor and resources. They are able to visualize and estimate WIP thresholds and estimate and size their work accurately and consistently in order to provide a true valuation of cost at each stage of the development.
Jira SAFe Technology Solution:Cprime was engaged to create, test, and implement a Jira SAFe solution that addresses the publishers challenges. Cprime’s Agile Coach and Jira Expert, Brandon Huff, determined the publisher needs to deliver an appropriate solution. Based on this solution, training was administered to establish common understanding and usage. Cprime’s Jira SAFe technology configuration unites the application of SAFe principles with key Jira functionality through a custom designed configuration. Cprime’s services, implementation and support bring together one ALM tool that provides visibility and comprehensive reporting needed for strong portfolio and program management. The Jira SAFe solution provides specific Jira elements at each SAFe Level – Portfolio, Program, and Team levels. The solution contains custom workflows for each portfolio, program and team level, custom fields and screens for each issue type (epic, feature, story, risk, spike, etc.). Cprime also configured Jira Agile Boards to help manage work and bridge together the SAFe hierarchy for value-stream reporting. Additionally, they established a hierarchy of issues across Portfolio, Program, and Projects to ensure visibility and planning.
Jira SAFe Technology Challenges:Cprime found the right blend of process and technology elements that aligned a unique pattern of technology, culture and org structure. The understanding of moving to the SAFe framework would allow for an easier standard of education, support and reporting. Cprime’s solution established principles that were configured to support process, terminology was defined, standardized and used consistently. The challenge that teams face with adopting SAFe and Jira “out-of-box” was that teams faced issues with a gap in nested and reportable issue hierarchies. There are usually naming challenges as many teams were running multiple projects with no standards defined.
Jira SAFe Solution Configuration:In order to configure the Jira SAFe solution, a number of elements were created and standardized in Jira.
Projects: Projects were created to allow specific permissions and visibility to each level of SAFe –Portfolio level, Program level, and Team level. While these are not actual projects, they are representative of the schemes to be applied at each level. It is recommended that this hierarchy be maintained for appropriate reporting and access.
Workflows: While a standard workflow works fine for smaller teams, dedicated workflows for Portfolio, Program, and Team are required to align with SAFe needs. Each Jira SAFe workflow was given custom states specific to each level to allow specific and simple reporting. This also avoids confusion when discussing the state of an issue.
Issue Types: We were able to leverage many of the existing and native issue types in Jira but some changes were made to the arrangement of the issues at each SAFe level. Natively, Jira Epics exist at the team level so they can own and manage their Epics. In SAFe, this ownership of Features would happen at the Program level and thus the issue type has been removed from the Teams.
Screens & Fields: Each Issue Type will have it’s own screen to allow specific fields to be associated with it. Additionally, a number of custom fields have been created to support the Jira SAFe solution. Many of these are based on SAFe concepts, analysis, and delivery.
Schemes: There are many configuration options in Jira for a project but, for ease of implementation, we only have a few schemes to apply to each project to implement Jira SAFe elements.
Agile Boards: Portfolio Board All Portfolio Project work is managed using a Kanban board. Since Epics will continually be identified and delivered, the Kanban board is ideal for this use.Program Board Like the Portfolio Project, the Program Project work is managed using a Kanban board. A Kanban board is also ideal for the Program level Features since work will continue to be identified and delivered. Team Boards The Team Projects are managed using a Scrum Board. This will allow the team to plan, commit, and deliver using Sprints. Additionally, the teams can leverage the reporting in Jira Agile. Relationship/Hierarchy Management: A solution was created to allow a hierarchy between all issues on all projects at all levels. This provided visibility and reporting on all work across the organization.
Jira SAFe Solution Outcome:One Integrated ALM Tool that Aligns Business & the Economic View “The business wants an IT organization that delivers consistently, faster, with quality, and can maintain a business-aligned economic view. To accomplish this we need tools which support a sound delivery process. We also need tools and processes that provide transparency in all aspects of our work (i.e., epics, features, stories, tasks, defects, spikes, risks, etc.) This process needs to enable our teams to move faster – and confidently. Realizing that much of our cost is in labor and resources – we need to be able to visualize and estimate our WIP thresholds, size our work accurately and consistently, and be ready to provide a true valuation of cost at every stage of development.”
Improved Value in Quality, Delivery and Process GovernanceOur ability to leverage our new SAFe version of Jira provides numerous reporting opportunities that we have never had. The net-net is that we are accomplishing a number of goals:
• A single ALM used by all our Agile teams – Jira. The benefit was a simpler training effort and comprehensive reporting.
• An effective tool that incorporates our newly adopted project management process – Jira SAFe. The benefit was a tool aligned to support the process, end-to-end visibility of Epics, Features and Stories.
• A single source entity for integration between Jira and Innotas. The benefit was a single source of Agile data, less labor need for reconciling, normalizing and integrating data”
Publisher Evaluation of Jira SAFe Solution:
Thought Leadership Expertise in Agile and Atlassian Products “Brandon Huff’s first visit was to provide a high-level overview class into the rudimentary uses of Jira Agile. This class was filled with people who wanted to delve deep into the Jira landscape. Brandon had to balance this advanced group with novice attendees who just needed to understand the fundamentals. They managed this delicate balance admirably. No one ever felt lost – or bored during the class. In fact, although I assisted in constructing the initial overview, Brandon really put together the final outline that was perfect for our initial goal: get people familiar with basic Jira. Brandon’s second visit was a bit different. Coming in, following the migration, we worked together to set up Jira SAFe in a way that aligned it with our implementation of the framework. There was a lot of coordination, collaboration, testing, and brainstorming. To be perfectly honest, as much as I wanted to work closely with him, there were times he had to grab me to ask a question or sit me down to make a decision on a path. I wasn’t the most accommodating person due to my daily distractions and business demands. Nonetheless, Brandon’s tactful “people” techniques demonstrated the following skills:
• He showed that he was a true Jira “Guru”. His high level of Jira expertise was often called upon to make numerous approach decisions based on little input or oversight from me. His decisions were always calculated and on the mark. It is a fact that he is a quick learner. Proof being that he was quickly able to understand our culture and traits during a very compressed time window. The result – I always had confidence in his judgment.
• He showed a tremendous degree of flexibility – At any time he could thoroughly walk us through a wide number of variations and options helping the team arrive at a sound approach or recommendation.
• His knowledge of SAFe and other processes were always evident and having that extensive background allowed him to make suggestions that were always well-thought-out on multiple levels – not just on the technical implementation of the tool. This meant he just didn’t do something because I told him so. If I suggested something that appeared flawed, he was quick to offer me the time to bounce it around and together come up with a more sensible approach.
• I hired Cprime as an expert in SAFe implementation using Jira. I never doubted, and They never gave me cause to doubt, that they were anything but that – Experts