Techniques to Scale Agile Across Project Teams and Organizations
Read on to learn about scaling Agile, product backlogs, building a collaborative culture, large-scale Agile frameworks, and Agile training courses and certifications.
Join the DZone community and get the full member experience.Join For Free
once associated only with small application development projects and co-located teams of 8-10 members, the agile methodology is now being adopted and adapted for large-scale enterprise development. the guiding principles of agile are to keep code simple, test often, and deliver working pieces of an application as soon as they're ready. how can companies take this approach and translate it to larger, enterprise-wide projects that need to scale across a wide variety of locations, lines of business, platforms, and technologies? this article offers some simple and effective techniques to help scale agile methodology across project teams and entire enterprises.
start with an mvp
before beginning your scaling agile journey, it helps to know where you want to end up. agile is all about short, flexible development cycles that respond quickly to customer demand. since you are, in effect, building a continuous, two-way software pipeline between you and your customers, you should have the idea of continuous delivery in mind from the start. continuous delivery is a software development strategy that optimizes your delivery process to get high-quality software into the hands of your customers as quickly as possible. the notion of releasing a prototype, or minimum viable product (mvp), is crucial for getting early feedback. once the mvp is released, you're then able to get feedback by tracking usage patterns, which is a way to test a product hypothesis with minimal resources right away. every release going forward can then be measured by how well it converts into the user behaviors you want the release to achieve. the concept of a baseline mvp product that contains just enough features to solve a specific business problem will also reduce wasted engineering hours and a tendency for feature creep or 'gold plating' among large, distributed software teams.
create a single product backlog
an agile product backlog is a set of tasks that must be finished before code can be released. scaling agile successfully requires that, instead of each agile team having its own backlog, product managers or owners need to maintain a single project-wide backlog for all teams so that high-priority tasks always receive immediate attention. this way, any contributor (including individuals, teams, departments, or even outsourcing firms) can pull tasks at any time from the top of the backlog onto their to-do list. a common backlog ensures that the highest-priority tasks are addressed first. if an urgent bug fix or a key customer feature request is placed at the top of the backlog, it will receive immediate attention instead of waiting for the next software iteration.
building a collaborative culture
in addition to having a group backlog, it's important to increase collaboration across organizational boundaries on large-scale agile projects, especially among analysts, developers, and qa testers. a successful scaled agile project is made up of energized, self-organized teams that operate with a minimum amount of supervision. one small way to encourage this kind of teamwork is via three amigos meetings, which involve a product owner (or a business analyst), a developer, and a qa tester who get together (either face-to-face or online) to review the requirements, tests, and dependencies of a feature request on the backlog. this often means that the product owner or an analyst, as a representative of the business, will take the lead and ask a programmer and a tester to look more closely at a feature.
in other cases, a programmer or tester may be the person initiating the meeting and setting the agenda. the advantage of three amigos meetings is that they provide orthogonal views on the feature under discussion. the business representative will explain the business need, the programmer will explain the implementation details and the tester will offer opinions on what might go wrong. three amigos meetings on scaled agile projects don't have to be limited to three people. in some cases, a tester might want advice from a security expert or a programmer may seek recommendations from a database or infrastructure person. the goal of a three amigos meeting should be to encourage at least three different viewpoints, as well as some kind of consensus about whether a feature is ready for further development. utilizing real-time agile test management tools can help aid the collaboration between project teams.
many organizations on an agile scaling journey also take the larger step of adopting a set of principles to guide their continuous delivery efforts, which can be helpful in outlining what type of collaboration they are trying to achieve. in implementing lean software development , mary and tom poppendieck show how the seven principles of lean manufacturing can be applied to optimize the entire software development process. these principles are:
- eliminate waste. lean manufacturing as practiced by companies like toyota regards any activity that does not directly add value to the finished product as waste. among the biggest sources of waste in software development are coding more features than required, task switching (assigning people to multiple projects), as well as delays caused by excessive documentation or management activities that prevent work from moving through a development organization in a just-in-time manner.
- build quality in. agile practices that build quality into your process include test-driven development (tdd) and development practices such as pair programming, continuous integration, and user experience design that helps the customer attain a feeling of perceived integrity.
(also known as "amplify learning"). this is where lean development differs from lean manufacturing. the poppendiecks compare development to a chef creating a recipe, while production is more like following the recipe in order to make the dish.
"recipes are designed by experienced chefs who have developed an instinct for what works and the capability to adapt available ingredients to suit the occasion."
according to the poppendiecks, development is a similar learning process involving trial and error. there is an expectation that mistakes will be made but developers will learn from them and make adjustments. strategies that promote amplified learning such as iterative development help teams discover what stakeholders want and act on that knowledge.
- decide as late as possible. keep your options open as long as practical, but no longer. delaying decisions is valuable because better decisions can be made when more facts are available. in an evolving software market, keeping design options open is more valuable than committing early. the most effective way to support your business such an environment is through a flexible, agile architecture that can tolerate change and by scheduling irreversible decisions to the last possible moment.
- deliver as fast as possible. rapid development has many advantages since it speeds up the discovery cycle (design, implement, feedback, improve) that is critical for learning. the shorter this cycle is, the more that can be learned. speed motivates teams to stay focused on continuously adding value by delivering shippable solutions on a regular basis and assures that customers get what they need more promptly.
- respect people. because decisions are made late and execution is fast, the use of a central authority to orchestrate the activities of workers is counter-productive. lean development calls for getting the details right and empowering the people who actually do the work since they're the ones who best understand the details. you need a management and governance strategy that focuses on motivating and enabling it teams, rather than controlling them
- see the whole. to effectively solve problems, you need to be able to look at the bigger picture. otherwise, you're at risk of falling into the trap of optimizing parts at the expense of the whole. it's important to understand the high-level business processes that individual projects support, processes that often work across multiple teams, technologies, and lines of business. measurements shouldn't be done at a level that promotes suboptimization, but by how well your entire team delivers overall business value.
these lean development principles are valuable for scaling agile projects in several ways, including helping you identify waste and then eliminate it. in addition to providing a philosophical foundation for your scaling agile project, the rules themselves are simple enough that they can be used as flexible guidelines to allow people on the ground the freedom to make their own decisions when dealing with contentious issues. as the poppendiecks caution in their book, however, implementing lean development requires a change in culture and organizational habits that some companies simply can’t achieve, but those that have understood and adopted the essence of lean thinking have realized significant, sustainable performance improvements.
large-scale agile frameworks
when scaling agile, it's important to use an approach that makes the most sense for your entire it organization. this may very well involve taking advantage of appropriate large-scale agile frameworks and/or body of knowledge. there are three major frameworks for scaling agile software development for large enterprises that have the most traction nowadays among agile enthusiasts: the scaled agile framework (safe), the disciplined agile delivery (dad), and large scale scrum (less). there are also a few other agile scaling approaches such as scrum of scrums (sos) that rely on informal or "roll your own" training, which may be worth considering if your organization has unique requirements that none of these three approaches address. (see richard dolman and steve spearman's comparative matrix that looks at several different agile scaling approaches.)
all three of the main scaling approaches offer multi-level training and certification, which make them attractive to enterprises wanting to expand a small agile group into an enterprise-wide practice and need formal guidance. take heed, however: some of these approaches call for a radical rethinking of a company's hierarchical organization, which may make it a hard sell in larger, traditional organizations with many layers and specializations.
the scrum process. all three scaled agile frameworks build upon techniques used in scrum and other lean and agile team-oriented frameworks. (source: lakeworks .)
because all three scaled agile frameworks build upon techniques used by team-oriented agile frameworks, it's important to have a basic grounding in the ideas, concepts, and terminology of scrum testing and other lean and agile frameworks. the safe framework defines group processes at the team, program, and portfolio level. safe teams typically consist of five to nine people who work in two-week scrums using xp (extreme programming) methods, pulling work from the program backlog. the length of each team's scrum is synchronized with five to 10 other safe teams at the program level (the next level up), as part of an agile release train that includes the development teams and other stakeholders. the highest level of the safe framework, the portfolio level, defines ways that executives and agile leaders can use lean processes like value streams to identify and prioritize features, which can then be broken down at the program level and scheduled on agile release trains.
this safe big picture graphic shows the three levels of safe (portfolio, program, team) as well as the many roles, ceremonies, and artifacts involved in safe. (source: scaled agile framework .)
disciplined agile delivery, developed by scott ambler and mark lines, is similar to safe in that it is built on existing lean and agile techniques. the dad framework is designed to work across three project phases: inception, construction, and transition. dad's strength is in providing more guidance in the areas of architecture and design, which occur at the inception phase earlier in a project's lifecycle. it's also strong at deployment (in the transition phase) since it has explicit devops practices and strategies built into the framework.
large-scale scrum (less), created by craig larman and bas vodde, has two frameworks: framework-1, designed for smaller companies (up to 10 scrum teams with seven members each) and framework-2, also referred to as less huge, designed for up to a few thousand people on one product. less expands on the basic team scrum framework by organizing several feature teams under a single product owner (po). framework-2 adds the notion of an area po (apo) to handle scaling in larger organizations. compared to safe and dad, less is a more flexible and non-proscriptive agile scaling framework, which may not make it the best choice for enterprises and large-scale development projects that need more structure.
training courses and certifications
for organizations that have decided to adopt a specific agile scaling framework, there are plenty of training courses and certifications to help you get up to speed on a particular framework. the scaled agile academy has a half dozen certifications that provide the knowledge and tools to be effective at the team, program and/or portfolio levels of the scaled agile framework. these range from two-day courses for managers and executives (safe agilist) to courses for developers and testers (safe practitioner) to an in-depth safe program consultant trainer program. the disciplined agile consortium, which oversees the dad framework, promotes five different certifications that range from a beginner stage, represented by disciplined agilist and certified disciplined agilist certifications, to a master stage, represented by the certified disciplined agile coach certification. there are several ways to learn more about less, including courses for certified less practitioner and certified less for executives .
most of the agile scaling framework courses listed here expect students to have basic scrum knowledge, which can be achieved by taking a certified scrummaster or a professional scrummaster course or by hands-on experience practicing scrum. the more experience your organization has with scrum and other lean and agile methodologies, the shorter your journey to scalable agile should be.
Published at DZone with permission of Francis Adanza. See the original article here.
Opinions expressed by DZone contributors are their own.