Agile at Scale

  1. Begin with an MVP: A Software Development strategy — Continuous Delivery provides quality, accessible software to customers/users. The Minimum Viable Product (MVP) release process is important for receiving early feedback and tracking use. It saves time and features such as gold plating amongst large teams.
  2. Create one backlog: The set of tasks to complete before release is listed and tracked on backlog. One backlog should be maintained by the Product Owner for all teams. One backlog allows focus on high priority tasks while providing access to all contributors at all times. Thereby preventing miscommunication and creating a collaborative environment.
  3. Setup a collaborative culture: Host meetings that include the Product Owner, a Developer and a Tester to asses requirements and test feature requests from the backlog in order to enhance teamwork. The Product Owner communicates the business need, the Programmer explains execution, and the Tester looks out for potential threats. This encourages different views while promoting unity with the team on the project.
  4. Adopt a large-scale agile framework: Examples of frameworks adopted in Agile at scale are the Scaled Agile Framework (SAFe), Disciplined Agile Delivery (DAD), Scrum of Scrums (SoS) and Large Scale Scrum (LeSS). These are perfect for small and growing organizations. A disadvantage is that these frameworks can lead to a restructuring of an organization, which can be challenging for large organizations.

--

--

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store