scalability requirements in user stories?

[dotnetguy]

Hello - How do you normally handle scalability requirements in user
stories? Do you simply include it in a section named "conditions of
satisfaction" like:

* Functionality should support 50,000 concurrent users

Or do you get scrummy with it and create a story that says:

"As a server I want to support 50,000 concurrent users so I can
support my expected demand and meet SLA's"

[George Dinwiddie]

Andrew,

On 11/13/12 6:15 PM, dotnetguy wrote:
> Hello - How do you normally handle scalability requirements in user
> stories? Do you simply include it in a section named "conditions of
> satisfaction" like:

A section of what?

> * Functionality should support 50,000 concurrent users
>
> Or do you get scrummy with it and create a story that says:
>
> "As a server I want to support 50,000 concurrent users so I can
> support my expected demand and meet SLA's"

I would never start with "As a server." I suspect there is some human
that wants to support 50,000 concurrent users. I also suspect there
needs to be a conversation about what "support 50,000 concurrent users"
actually means.

- George

--
----------------------------------------------------------------------
* George Dinwiddie * http://blog.gdinwiddie.com
Software Development http://www.idiacomputing.com
Consultant and Coach http://www.agilemaryland.org
----------------------------------------------------------------------

[Joerg Henning]

Agree with George. Usually this comes from somebody in the organization, probable the management, or sthg. 

However, I wonder if SLA's like this is really makes sense as a story as they not really a single-Sprint effort but needs to be applied and verified continuously. More a matter of quality than of features.

To make sure there continuously applied, I would write them down, make them available to the team and put "System is load tested and conforms to SLA's according to Document XYZ" into the DoD.

Regards,

Joerg

--
You received this message because you are subscribed to the Google Groups "Scrum Alliance - transforming the world of work." group.
To post to this group, send email to scruma...@googlegroups.com.
To unsubscribe from this group, send email to scrumalliance+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/scrumalliance?hl=en.

--
joerg henning / software developer & scrum master
mobile: +84 1283 362 461
skype: henning.joerg

mail: house 8 / alley 124/22/75 au co / tu lien ward / tay ho district / ha noi / vn

[dotnetguy]

@George - That's a good point that scenarios should be defined for
load requirements. For example, 50K concurrent users trying to view a
cached report is different than 50K concurrent users trying to save a
vote into the Votes table for American Idol.

@Joerg - Including a general scalability statement as you mentioned in
DoD sounds like a pretty good idea too.

> >  ------------------------------**------------------------------**
> > ----------

> >   * George Dinwiddie *                      http://blog.gdinwiddie.com
> >   Software Development                    http://www.idiacomputing.com
> >   Consultant and Coach                    http://www.agilemaryland.org

> >  ------------------------------**------------------------------**
> > ----------

>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Scrum Alliance - transforming the world of work." group.

> > To post to this group, send email to scruma...@googlegroups.com**.
> > To unsubscribe from this group, send email to scrumalliance+unsubscribe@**
> > googlegroups.com <scrumalliance%2Bunsu...@googlegroups.com>.
> > For more options, visit this group athttp://groups.google.com/**
> > group/scrumalliance?hl=en<http://groups.google.com/group/scrumalliance?hl=en>
> > .
>
> --
> *joerg henning /** *software developer & scrum master

> mobile: +84 1283 362 461
> skype: henning.joerg
> mail: house 8 / alley 124/22/75 au co / tu lien ward / tay ho district / ha

> noi / vn- Hide quoted text -
>
> - Show quoted text -