Scrum/Agile

96 views
Skip to first unread message

crow

unread,
Nov 11, 2008, 8:55:07 AM11/11/08
to Volere Requirements
Hi -- I'm a business analyst at a commercial software company. My
company is beginning to use scrum to develop a new product in an
existing market. I'm interested to hear from others who have
experience with this process. Candidly, I've read a bit on the 'net
and am more confused.

- Is there a place for traditional functional requirement statements
in scrum?
- If so, when are these actually written?
- How does Volere fit with scrum?
- Recommendations on books that might help someone new to scrum.


Thanks very much for any insights.

Robrecht

unread,
Nov 25, 2008, 5:25:13 AM11/25/08
to Volere Requirements
Crow

My suggestion:
- use Volere to add discipline to your requirements engineering.
- use a lean approach (scrum) to decide when you will write your
requirements.

Scrum puts all work to be done in a product backlog. A list of stories
that deliver value (a slice of functionality) to the user. Volere
tells us to look for the business use cases first and then decide on
the scope and calling these product use cases. Put these (product use
cases) as stories on your product backlog.
Then describe the requirements associated with these stories, put
effort only on those things that are really required (required: => it
must be so, it cant be any other way).
Your backlog items are then the starting point for your conversation
with the development team. They can suggest any other solution as long
as the solution complies with the requirements.

Agile and Iterative Development by Craig Larman
Agile Estimating and Planning by Mike Cohn
Agile Project Management with Scrum by Ken Schwaber

Hope this helps

Robrecht DAVID
robrech...@ae.be
mobile +32 496 59 50 44

ae nv/sa n architects for business & ICT n www.ae.be

Interleuvenlaan 27b, BE-3001 Heverlee
tel +32 16 39 30 60, fax +32 16 39 30 70

crow

unread,
Nov 26, 2008, 8:34:30 AM11/26/08
to Volere Requirements
Thanks very much David! It makes sense to associate the PUC's with
the user stories.

It sparked a few more questions to draw on your or the group's
experience:
-- Does the entire scrum team work together to ferret and flesh out
the requirements?
-- How have you seen the role of the business analyst change?

And thanks again for the book recommendations. I'll check them out.

On Nov 25, 5:25 am, Robrecht <robrecht.da...@ae.be> wrote:
> Crow
>
> My suggestion:
> - use Volere to add discipline to your requirements engineering.
> - use a lean approach (scrum) to decide when you will write your
> requirements.
>
> Scrum puts all work to be done in a product backlog. A list of stories
> that deliver value (a slice of functionality) to the user. Volere
> tells us to look for the business use cases first and then decide on
> the scope and calling these product use cases. Put these (product use
> cases) as stories on your product backlog.
> Then describe the requirements associated with these stories, put
> effort only on those things that are really required (required: => it
> must be so, it cant be any other way).
> Your backlog items are then the starting point for your conversation
> with the development team. They can suggest any other solution as long
> as the solution complies with the requirements.
>
> Agile and Iterative Development by Craig Larman
> Agile Estimating and Planning by Mike Cohn
> Agile Project Management with Scrum by Ken Schwaber
>
> Hope this helps
>
> Robrecht DAVID
> robrecht.da...@ae.be

Robrecht David

unread,
Nov 28, 2008, 5:45:02 AM11/28/08
to vol...@googlegroups.com
Crow

The PO or PO team should be able to explain the requirements. As far as they are Business requirements.
When you need or want to add functional requirements it could be the PO or the team. Within the team you can have specialisation towards this.
As far as the BA role goes have a look at this:

http://www.linkedin.com/groupAnswers?viewQuestionAndAnswers=&gid=105958&discussionID=569430&sik=1227868977307&trk=ug_qa_q&goback=%2Eana_105958_1227863817855_1%2Eana_105958_1227868977307_1

Robrecht DAVID
robrech...@ae.be
mobile +32 496 59 50 44

ae nv/sa n architects for business & ICT n www.ae.be

Interleuvenlaan 27b, BE-3001 Heverlee
tel +32 16 39 30 60, fax +32 16 39 30 70
________________________________________
Van: vol...@googlegroups.com [vol...@googlegroups.com] namens crow [Cro...@gmail.com]
Verzonden: woensdag 26 november 2008 14:34
Aan: Volere Requirements
Onderwerp: Re: Scrum/Agile
Reply all
Reply to author
Forward
0 new messages