Back to Forum

Automated build

Last post 03:56 pm November 19, 2018 by David Castellanos Flores
3 replies
srini p
02:51 am February 21, 2017

I had question regarding the automated build , when the automated build should be created for the project, as there is no sprint 0 as part of scrum standards, when should one create  any of these setup type of  activities

Ian Mitchell
05:07 pm February 21, 2017

In the very first Sprint, so that an integrated increment of value can be delivered by the end of it and each subsequent Sprint.

The first few Sprints may involve more setup work than later ones. What matters is that each Sprint time-box is respected and a valuable increment is always provided, no matter how small. For example, a valuable increment may consist of one or two small features or user storieswhich serve to validate whatever architecture, environments, test harnessing or infrastructure is being set up.

srini p
01:53 am February 22, 2017

So it should be created  as soon as initial code is in source control?

David Castellanos Flores
03:53 pm November 19, 2018

automated builds are not part of scrum. 

Implement automated build it is a decission for the development team. But the "build" is what you are going to send to the stakeholders, and maybe the PO can decide to do it automatically to ease the process. 

 

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.