Back to Forum

Build Team

Last post 05:52 am October 10, 2014 by Ian Mitchell
2 replies
Salaivan Muthu Sampath
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 ?

Ludwig Harsch
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.

Ian Mitchell
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.

By posting on our forums you are agreeing to our Terms of Use.

Please note that the first and last name from your Scrum.org member profile will be displayed next to any topic or comment you post on the forums. For privacy concerns, we cannot allow you to post email addresses. All user-submitted content on our Forums may be subject to deletion if it is found to be in violation of our Terms of Use. Scrum.org does not endorse user-submitted content or the content of links to any third-party websites.

Terms of Use

Scrum.org may, at its discretion, remove any post that it deems unsuitable for these forums. Unsuitable post content includes, but is not limited to, Scrum.org Professional-level assessment questions and answers, profanity, insults, racism or sexually explicit content. Using our forum as a platform for the marketing and solicitation of products or services is also prohibited. Forum members who post content deemed unsuitable by Scrum.org may have their access revoked at any time, without warning. Scrum.org may, but is not obliged to, monitor submissions.