Successful agile teams can produce higher-quality software better meeting user needs quicker and at a lower cost. Transitioning to an agile process like Scrum, however, can be challenging but forethought and working with experienced coaches and trainers will help.
What is an agile methodology?
An agile methodology—such as Scrum—is a lighter weight approach to software development than many of the traditional approaches.
Agile methodologies feature self-organized teams that are empowered to achieve specific business objectives. Agile methodologies focus on rapid and frequent deliverables of partial solutions that can be evaluated and used to determine next steps.
In this way, solutions are built in an iterative and incremental manner. Agile methodologies have been shown to deliver higher quality products in less time, resulting in improved customer satisfaction.
Is it best to run an agile software development pilot project first?
It is not necessary to run an agile software development pilot project. Pilot projects are commonly done for two reasons: To see if something will work or to learn how to make it work.
By now, enough other companies—very likely including some of your competitors—are using agile approaches like Scrum so that there is no longer any question of if it works.
The real question most organizations face is how to make agile or Scrum work for them. One or more software development pilot projects can be very helpful in providing those answers.
Should we convert all at once to agile methodologies?
Most organizations still begin with a handful of teams and spread their Scrum or agile software development process across the organization. But, all-in transitions are becoming more common.
During their first year of using Scrum, Salesforce.com reported releasing 94 percent more features, delivering 38 percent more features per developer and providing over 500 percent more value to customers compared to the previous year.
How quickly can we become agile?
You'll see the benefits of adopting agile software development certainly within the first year and most likely within the first three to six months.
Keep in mind that many organizations go through a period of turmoil during the first one to three months as some people resist the change and others face legitimate hurdles in overcoming years of ingrained behavior.
Remember, though, that agile is not something you work at and then suddenly become. As you approach what you think of today as agile, you'll realize there's always further to go.
How do I get started with agile software development?
The approach we advocate is to iterate toward agility. Create an improvement backlog of all the things your organization could do better or could do in a more agile manner. Invite others to join this effort, particularly those with a passion for improving the development process or with agile experience either in your company or with a prior employer.
If your improvement backlog is long, consider grouping the items to create multiple improvement backlogs. Publicize the change effort to company employees and seek volunteers to work as a community toward making these improvements. As these improvement communities form, let each own one of the subdivided improvement backlogs.
If the transition effort warrants it, establish an Enterprise Transition Community that provides energy, support, resources, guidance and occasional direction to the improvement communities who are doing the real work of driving the agile transition across the company.
Recommended Resources Related To Agile Software Development
Four Types of Resistors When Adopting Agile
Four Attributes of the Ideal Pilot Project
Choosing to Start Small or Go All In when Adopting Agile
Selecting a Development Process
Agile and Scrum for Video Game Development