Skip to main content

A question about development team

Last post 09:19 am February 15, 2016 by Pradip Kumar Ghosh
8 replies
06:33 pm February 11, 2016

When does a Development Team make adjustments to its engineering practices?


According to my knowledge the answer is.. After they have been discussed and agreed to at the Sprint Retrospective.

please, clarify my doubt


12:32 am February 13, 2016

Any time as necessary. Development teams should be adaptive / flexible.


01:34 pm February 14, 2016

As per Scrum Guide one of the purpose of Sprint Retrospective is "Inspect how the last Sprint went with regards to people, relationships, process, and tools". So in this event process & tools will be inspected & adapted.


02:16 pm February 14, 2016

The Scrum Guide says that "each event in Scrum is a formal opportunity to inspect and adapt something".

Do you think there might be other opportunities to inspect and adapt "engineering practices" apart from during a Sprint Retrospective? When might a team reconsider, for example, how members work together and self-organize with a particular accomplishment in mind?


11:19 pm February 14, 2016

Hi Ian I agree that each event in Scrum is a formal opportunity to inspect and adapt something but I feel that "engineering practices" are process & tool for team to use. Among the 4 events Scrum Retrospective is the best to inspect & adapt the "engineering practices".

Kindly clarify & I know you can provide the best answer to any question. :)


01:26 am February 15, 2016

The question asked is: "When does a Development Team make adjustments to its engineering practices?"

Engineering practices are the means by which sprint increments are built. A Sprint Retrospective is an opportunity for the whole Scrum Team to inspect and adapt its ways of working for future sprints.

What event does a Development Team uniquely participate in however, so it can adjust the engineering of a specifically planned increment?


02:20 am February 15, 2016

Ian I can understand that it will be "Daily Scrum" where Development Team uniquely participate & as per you there only Dev team will adjust their engineering practices.

Ian I am just trying to understand different inherent assumptions in this question that's why I am asking so many question & giving my point of view. I might be wrong in interpreting this.

Do you mean to say that for ongoing sprint it will be "Daily Scrum" where Dev Team will adjust/adapt their engineering practices.

If adjustment/adaptation is done in a Sprint Retrospective then it will be applicable for future Sprints?

Also Scrum guide says "The Development Team uses the Daily Scrum to inspect progress toward the Sprint Goal and to inspect how progress is trending toward completing the work in the Sprint Backlog." So, main inspect & adapt during Daily Scrum is Sprint Goal & Sprint Backlog, then when/how/why team will do adjustment to their engineering practices in Daily Scrum.


03:16 am February 15, 2016

> Do you mean to say that for ongoing
> sprint it will be "Daily Scrum" where Dev
> Team will adjust/adapt their engineering practices.

Yes.

> If adjustment/adaptation is done in a
> Sprint Retrospective then it will be
> applicable for future Sprints?

Yes.

> ...main inspect & adapt during Daily
> Scrum is Sprint Goal & Sprint Backlog,

Correct.

> then when/how/why team will do
> adjustment to their engineering
> practices in Daily Scrum.

The Sprint Backlog represents a technical plan for implementing the Sprint Increment. It is wholly owned by the Development Team. The Sprint Backlog can be expected to describe how engineering practices will be applied by that team and in what order. These may include tasks for peer review, test-driven development, architectural refactoring, configuration management, or indeed any other practices that the team believes it should apply. Some practices may be quite specific to the Product Backlog Items selected. All are subject to potential adjustment in each Daily Scrum.


09:19 am February 15, 2016

Thanks a lot Ian. I am really happy to get so many learning from this discussion. You are amazing & you have best & most detailed answer to any question. :)


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.