Enterprise Agile

Embracing Agile from teams to the Enterprise

 

Enterprise Agile aims to bring the advantages of Agile - rapid feedback, quick response to change, incremental development - at the enterprise level.

Enterprise Agile is typically implemented top-down and is a key element of digital transformation for IT organizations and software development.

The practice of Enterprise Agile encompasses lean portfolio management, agile funding and budget management, agile team run and reporting, and scaled agile, which is the agile development and release of initiatives involving multiple Agile teams.

Interested in SAFe?
Planisware is a Platform Partner of Scaled Agile, the institute behind the mainstream methodology.

 

10 Enterprise Agile Requirements
you should consider implementing

Enterprise Agile at the Portfolio Level

  1. Development value streams gather all the activities contributing to the development of new services and products. They have a dedicated budget and large initiatives - such as epics and release trains - that contribute towards their goals.
  2. Portfolio and product Roadmaps are the embodiment of the portfolio / product strategy within a timeframe. Roadmaps include all relevant direct and indirect activities, along with external events or factors driving the development. 
  3. Control of delivery is ensured by refining Epic outcomes into capabilities and features. At each step, a backlog is used to keep track of the remaining activities. Priority is managed in multiple ways: must-dos, WSJF - Weighted Shortest Job First -, scoring, etc.
  4. Progress is tracked through the visible achievements of the teams, such as demos or mock-ups, and through objectives, which can be used to measure the value delivered by the teams.
  5. Agile reorganizes work around permanent objects such as value streams at the portfolio level, or services and products at the team level. Work is carried out by stable, self-sufficient teams.
Portfolio Kanban

 

Enterprise Agile at the Execution Level

  1. Organize, track and forecast work through release planning - called PI planning within the SAFe methodology. Make sure teams are synchronized, deploy on cadence, and that cross-team dependencies are accounted for.
  2. While the team is autonomous and responsible to deliver on the sprints and stories, make sure that the most important features are prioritized through robust backlog management.
    and also: Use the most appropriate agile work logic. Either release incrementally by organizing delivery through sprints with scrum teams, or continuously, with kanban teams and swimlanes.
  3. Time tracking supports the CAPEX computation and keeps track of cost and time spent at different levels of granularity. In addition, such tracking gives visibility into how much time goes towards "keep the lights on" activities, or could be charged back.
  4. Communication within or among teams is carried out by a variety of means: social feeds, chats, documents, tasks, and alerts to name a few. Regardless of distance and timezone, all stakeholders must remain in touch. Keep track of discusions, retrospective analysis, and decisions through meetings, agendas, and minutes.
  5. Manage the lifecycle of your products and services: consolidate test results, defects, profit and loss, communications, and team contributions in a single system to build visibility.
Sprints

 

From teams to global: DevOps tool consolidation

Letting teams decide and opt for the tools they prefer to do their work falls under the self-organizing and trust section of the Agile principles.

Your teams may opt to work directly within one of the Planisware solutions, but many already have their own development workflows and tooling in place.

DevOps tool set-ups necessarily vary from one team to the next according to the team's needs and focus; the traditional approach of setting up a "standard" one-size-fits-all connector therefore does not work.

Planisware pushes the definition of the connector to the team level, where decisions about granularity and objects being consolidated make the most sense.

 

Planisware and SAFe
the scaled agile methodology for large teams

Planisware SAFe capabilities demonstrated at both the Team, Train, and Portfolio levels. In this video we 1] introduce the SAFe framework in a pragmatic way, and 2] show how to support a Scaled Agile process that follows SAFe principles.

Subjects covered:

  • Release trains
  • Program Increment (PI) Planning
  • Backlog management and prioritization (using WSJF)
  • Program boards
  • Team breakouts & boards
  • Team management
  • Agile sprint within Planisware and Jira Integration
  • Epic & features
  • Features estimates & scoring (WSJF)
  • Portfolio prioritization
  • Value Streams / Strategic themes (budgets)
  • Portfolio kanban

 

 

Embrace the Agile Transformation

 

Ready to learn more? Explore our solutions.

Strategic Portfolio Management at Scale
Advanced, from strategic planning to delivery

Deliver your projects and portfolios at scale

Planisware Enterprise captures your strategy and aligns your portfolios, projects, and teams to make an impact on the bottom line.

Learn moreGet the brochure

Adaptive Project Management at its Best
All-around, from portfolios to execution

Onboard your data and personnel fast.

Planisware Orchestra enables project decision-making across the entire portfolio and helps you reach the next maturity level.

Learn moreGet a free trial