Skip to main content

Enterprise moving to Agile Adoption

Last post 06:03 pm January 11, 2017 by Ian Mitchell
6 replies
07:05 am January 7, 2017

With most enterprises adopting Agile, how does the horizontal testing functions like Automation, performance, Test Data Management get aligned to the two week Sprint?
Example: In some cases, the Test Data itself could take a day or two with limited environment availability.


02:51 am January 10, 2017



The only expected output from a Sprint is Potentially Releasable Increment so list down the activities required to make your software releasable every Sprint and decide your Sprint length accordingly, should not be more than 30 days.

Also find out what is stopping you from releasing your software every Sprint and work on removing those impediments.


06:07 am January 10, 2017

Your testing functions like Automation all should be discussed in Sprint planning, it will go as an Item in Sprint, which will be estimated and worked on. Testing could be one of the item in Definition of done to complete a User story/task.


12:34 pm January 10, 2017

This may sound obvious, but as the potentially releasable product is expected at the end of the Sprint, the options are limited - so either cut-short on your test scripts to choose most important ones first which can be done within 2 weeks OR increase your sprint duration to max 4 weeks.
In my experience, many projects do not necessarily deploy at the end of each sprint, but by running the sprints keep the things tidy until a point comes where you decide its the time to now go live.

Pankaj


06:38 pm January 10, 2017

> With most enterprises adopting Agile, how does the horizontal
> testing functions like Automation, performance, Test
> Data Management get aligned to the two week Sprint?
Example: In some cases, the Test Data itself could take a day
> or two with limited environment availability.

Can you clarify the issue here? Why would a couple of days work on certain tasks needed for a Done increment cause an problem?


04:41 am January 11, 2017

Thank you for the response.
The problem is that, we have a Horizontal team accpeting the requests from all the applications, working on them and delivering it. With Organization focus towards Agile, how does the Horizontal teams fit in Agile? How will they operate in an Agile mode? Can they still continue being Horizontal?


06:03 pm January 11, 2017

The best strategy is to form feature teams, each of which has the skills to complete a vertical slice of integrated and usable functionality. That is how MVP increments are typically framed and delivered. Deferring delivery until horizontal slices are integrated is a difficult thing to reconcile with agile practice.


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.