Welcome to Scribd, the world's digital library. Read, publish, and share books and documents. See more
Standard view
Full view
of .
Look up keyword
Like this
0 of .
Results for:
No results containing your search query
P. 1
Lecture 18 SLIDES WITH NOTES – getting things done: agile, lean & startups

Lecture 18 SLIDES WITH NOTES – getting things done: agile, lean & startups

Ratings: (0)|Views: 709|Likes:
Published by danmcquillan
Lecture 18 SLIDES WITH NOTES – getting things done (agile, lean & startups)
Lecture 18 SLIDES WITH NOTES – getting things done (agile, lean & startups)

More info:

Published by: danmcquillan on May 27, 2012
Copyright:Attribution Non-commercial


Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less





So-called lightweight software development methodsevolved in the mid-1990s as a reaction againstheavyweight methods, which were characterized bytheir critics as a heavily regulated, regimented,micromanaged, waterfall model of development.Proponents of lightweight methods (and now agilemethods) contend that they are a return todevelopment practices from early in the history ofsoftware developmenthttp://en.wikipedia.org/wiki/Agile_software_development iterative and incrementalcollaborationadaptivehttp://en.wikipedia.org/wiki/Agile_software_development
Agile Backlog (critical tasks at bottom, less critical above, unclassified at right)
The product backlog is a prioritized features list, containingshort descriptions of all functionality desired in theproduct.QUESTION: what kind of things do you think should go in abacklog?A typical product backlog comprises the following differenttypes of items:FeaturesBugsTechnical workKnowledge acquisitionTechnical work and knowledge acquisition activities alsobelong on the product backlog. An example of technical work would be, "Upgrade all developers' workstations toWindows 7." An example of knowledge acquisition couldbe a product backlog item about researching variousJavaScript libraries and making a selection.http://www.mountaingoatsoftware.com/scrum/product-backlog
By far the predominant way for a Scrum team to express featureson the product backlog is in the form of user stories, which areshort, simple descriptions of the desired functionality told fromperspective of the user. An example would be, "As a shopper, Ican review the items in my shopping cart before checking out sothat I can see what I've already selected."Think of user stories as representing a collaboration between thecustomer and the developers, as opposed to documentingcustomer requirements. The purpose of this collaboration is toreveal and understand the details of the user stories, which arerecorded in the confirmation.Some people write a short description of the user story on theindex card, while others like a statement of the format: [Role]can [capability], so that [benefit] .The customer writes the user stories because she’s in the bestposition to know the desired functionality. Each user story mustbe written in the language of the business. This enables thecustomer to prioritise the user stories according to their value tothe business and their cost, and select the user stories for eachiteration. The developers can assist the customer but theresponsibility for writing stories must reside with the customer.http://www.energizedwork.com/weblog/2006/02/user-stories-part-1- what-is-user-story.html 

You're Reading a Free Preview

/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->