GSA/christopher

View on GitHub
_guides/applying_agile_practices.md

Summary

Maintainability
Test Coverage
---
title: Applying Agile Practices to Business Teams
category: Agile
audiences:
  - Developers
  - Designers
  - Project Managers
---
  
### If Not Software Development, Then “Who…?”
Agile practices have proliferated into business lines such as [Marketing, Human Resources, Legal]({{ site.baseurl }}/guides/agile_adoption/#agileculturebenefits), and beyond. Agile can not only transform an organization’s approach to software development, but also its enterprise departmental functions, project management practices, and product development. Moreover, in order to survive an ever-changing environment, creating more innovative, cross-functional, and multidisciplinary teams that generate growth and increased skillsets has become paramount - across the _**entire**_ organization. Taking an Agile approach can boost self-organization and employee engagement among business teams while breaking organizational silos that present barriers to communication and collaboration.

As self-organization and skillsets grow, barriers are broken down, collaboration increases, and a business team’s agility matures. As Rigby, et al. state in Embracing Agile, “as an organization progresses in Agile adoption, they must extend beyond the vocabulary and create a supportive environment that embolden the “[conditions for Agile](https://hbr.org/2016/05/embracing-agile).” The favorable conditions for Agile - based on the *market environment, customer involvement, innovation type, modularity of work, and impact of interim mistakes* - extend beyond developing software. While they affect many development functions, the authors also note these conditions apply to “marketing projects, strategic-planning activities, supply-chain challenges, and resource allocation decisions.”

### Adapting Agile Behavior
The key to broadening Agile adoption is the adaption of new mindsets and behaviors of the individuals that make up the business team. It begins with creating visibility and transparency of work, systems-based or otherwise. Over time, mindsets change as individuals continue to adapt more Agile behaviors, such as:
* Breaking down project work, or initiative-based tasks, into iterations (i.e. sprints),
* Creating a backlog of prioritized projects and tasks,
* Setting and working in iterations, or sprints, with agreed goals,
* Creating a “working board” of projects and tasks, (which can be supported by a tool),
* Scheduling daily 15-minute check-ins (instead of holding lengthy staff meetings), and
* Focusing on velocity / capacity, versus speed.

First, Agile behaviors are not beholden to any one framework (i.e. Scrum, Kanban, etc.) and can conceivably be implemented without one. These behaviors simply help establish a more transparent, collaborative Agile environment, even beyond software development. 

Second, Agile behaviors not only accommodate visibility of the business team’s work, but allow for better prioritization and breakdown of project work and tasks. They also support the setting and achievement of short, targeted goals and increase collaboration among team members. Finally, Agile behavior encourages communication of progress within and outside the team, without adding lengthy meetings that take away from prioritized work.

### Creating a Responsive Environment
In addition to changing the mindsets and behaviors of the business teams, the organization itself must also adapt. As Agile adoption progresses, the organization must champion a supportive environment that enables its individuals to better respond to change and shifts the measurement of success and business value to meeting customer needs. According to the [Agile Alliance](https://www.agilealliance.org/agile101/), **Agile is “the ability to create and respond to change in order to succeed in an uncertain and turbulent environment.”** That responsiveness is matured over time through the incorporation of customer-focused, cost-effective Agile practices.

Like software development, an organization’s business departments, project management offices, and product development also face complex problems - often with many unknowns or changing requirements that can only be addressed as more information becomes available. By breaking efforts down, partnering with end users / customers to obtain rapid feedback, and eliminating silos through cross-functional collaboration, these groups can leverage an Agile approach in order to face challenges in a more responsive manner. Organizations can support the agility of these groups through encouraging the adaption of Agile behaviors and by creating a responsive environment.

For more information on how specific domains are applying Agile practices to their business, check out the following:
* [Applying Agile Practices - Agile Human Resources (HR)]({{ site.baseurl }}/guides/applying_agile_practices_HR/)
* [Applying Agile Practices - Agile Legal]({{ site.baseurl }}/guides/applying_agile_practices_legal/)
* [Applying Agile Practices - Agile Marketing]({{ site.baseurl }}/guides/applying_agile_practices_marketing/)

### Good Reads
These are good references for understanding the application of Agile practices to Business Teams:
* [6 agile principles that apply to everything](http://www.cio.com/article/2971822/agile-development/6-agile-principles-that-apply-to-everything.html)
* [7 aspects of Agile HR](https://hrtrendinstitute.com/2015/02/14/7-aspects-of-agile-hr/)
* [Agile Alliance: Agile 101](https://www.agilealliance.org/agile101/)
* [Agile HR: Transforming a Human Resources Team Using Scrum](http://www.slideshare.net/seedbox/hr-programspublic?next_slideshow=1)
* [Agile Marketing Manifesto](http://agilemarketingmanifesto.org/)
* [Agile Marketing Manifesto Explained](http://theagilemarketer.net/agile-marketing-manifesto-explained/)
* [Bring Agile to the Whole Organization](https://hbr.org/2014/11/bring-agile-to-the-whole-organization)
* [Building the Agile Enterprise](http://www.slideshare.net/jbersin/impact-2012-keynote-josh-bersin)
* [Embracing Agile](https://hbr.org/2016/05/embracing-agile)
* [How NPR benefits from agile project development & you can too](http://www.poynter.org/2012/how-npr-benefits-from-agile-project-development-you-can-too/175487/)
* [How to apply Agile practices with your non-tech team or business](http://www.techrepublic.com/article/how-to-apply-agile-practices-with-your-non-tech-team-or-business/)
* [Organisational agility: How business can survive and thrive in turbulent times](https://www.emc.com/collateral/leadership/organisational-agility-230309.pdf)
* [Scaling Agile at Spotify](https://techcrunch.com/2012/11/17/heres-how-spotify-scales-up-and-stays-agile-it-runs-squads-like-lean-startups/)
* [The Dawn of the Agile Attorney](http://www.lawpracticetoday.org/article/dawn-agile-attorney/)
* [What is Agile HR? And is it right for you?](http://www.hrsg.ca/what-is-agile-hr-and-is-it-right-for-you/)