All About Agile | Agile Development Made Easy!

Agile Scrum vs. Change Management

Here's the Scenario:

The Scrum team (Consultants) is doing well in Release 10, Sprint 2. The client (waterfall) is looking at Release 1, sprint 1 and is looking at production and saying, "Hey! Production doesn't match your Requirements!". Of course not, the current state production version has changed 10 times! So, how does the team deliver (to the client) a document that shows current state? Giving them a stack of user stories isn't a real option. What artifact shows current state of development?

Thanks,

Raymond

Add a Comment

You need to be a member of Agile Community to add comments!

Join Agile Community

Comment by R on February 23, 2012 at 17:17: Yes, Klaus. All reviews done for every sprint as needed.

Comment by R on February 3, 2012 at 14:15: Thanks, Klaus Even Enevoldsen!

I have studied Scrum, and had never seen it, so I figured as much. Thanks for your solution.

Everyone Else: What are YOU doing to satisfy the QA folk?

Comment by Klaus Even Enevoldsen on February 3, 2012 at 13:06: This is one of the situations where Agile meets reality: “We value working software over comprehensive documentation”.

I am a ScrumMaster in a medical company and we have a similar issue. We need to document that everything is tested and we must be able to provide traceability.

In Waterfall you typically use the V-model and a traceability matrix – QA people love these things. J So what we do is to do a mini-V in the end of every sprint – and update the documentation with every sprint. There are tools to help with that we use Microsoft Team Foundation Server.

Comment by R on February 3, 2012 at 11:44: Correct. Made 9 Releases to Production, each one had all spring reviews with client. The client QA group is trying to fill out their Requirements paperwork. It makes sense that the client would need to validate that we are producing (production app) what we promise(user stories aka requirements). I have nothing but a stack of user stories that are an iterative story. No one document that shows what the requirements are of the *Current* production application.

*** What is that document ? ***

Raymond

Comment by Klaus Even Enevoldsen on February 3, 2012 at 9:04: Hi,

I need to understand this.

1) You have made 9 releases and is working on the 10. release?

2) You have deployed the ninth release to production?

3) Have you held any Sprint Reviews with the customer?

Thanks,

Klaus