Enterprise Agile aims to bring the advantages of Agile - rapid feedback, quick response to change, incremental development - at the enterprise level. The practice of Enterprise Agile encompasses lean portfolio management, agile funding, agile team, and scaled agile - initiatives involving multiple agile teams.
10 Enterprise Agile Requirements you should consider implementing
Enterprise Agile at the portfolio level
- 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.
- 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.
- 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.
- 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.
- 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.
Enterprise Agile at the execution level
- Organize, track and forecast work through release planning - Program Implement (PI) Planning within the SAFe methodology. Make sure teams are synchronized, deploy on cadence, and that cross-team dependencies are accounted for.
- 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. 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.
- 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.
- 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.
- 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.
Keep your global team connected: DeveOps 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
Planisware SAFe (the Scaled Agile Framework) 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.