Build Team

Last post 05:52 am October 10, 2014
by Ian Mitchell
2 replies
03:16 pm October 6, 2014

Currently we are moving from Waterfall to Agile - and in waterfall we have dedicated Build team to deploy the build in DEV/INT/CERT/PROD environments... Since we are moving towards Agile - how we can place the build team ?

05:19 am October 9, 2014

What do the team members think about this?
How many people are working on the product in total, including the build team?
There are several ways to organize teams in scaled Scrum.
You can build feature teams which are able to deliver new functionality without the help from other teams. Each feature team could include one person from the current build team.
Or you can build component teams, each responsible for one component. You can also have an integration team (or build team).
It is however important that the teams share a common definition of done to ensure their work integrates and is potentially shippable.
Ask the people who do the work which model they prefer.

05:52 am October 10, 2014

In Scrum an increment should be potentially releasable as per the team's Definition of Done. A team should try to improve their DoD so each increment is delivered into an environment that is as close to production as possible.

This implies that your Development Teams should seek to deploy each increment into PROD. Whether or not they need to go through the elevations of DEV/INT/CERT beforehand is up to them as self-organizing teams that both follow and inform organizational standards.