jlinks

Independent Negotiable Valuable Estimable Small Testable

To understand scrum, you should know where it comes from. Best and shortest story is the agile manifesto : Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan See also:  http://scrumtrainingseries.com Scrum is an implementation of agile, which has: - Product Backlog List of INVEST Product Backlog Items (PBI) written and maintained by Product Owner INVEST:  Independent, Negotiable, Valuable, Estimable, Small, Testable PBI should idealy not take more than 2-3 days to develop. Do a Who/What/Why check for every PBI - Backlog grooming -- 1 hour (team + owner + master) prioritize / clarify / split large and estimate (S/M/L/XL) PBIs  (next sprints) add / remove / reprioritize the backlog if necessary - Sprint Plannung 1 -- 1 hour (team + owner) go through "READY" and prioritized PBIs (stories) ...

"people tend to want to know something about the other members;  have to develop a degree of interdependence in order that the group or team may achieve its tasks and be satisfying to its members; and has to learn at some level to deal with conflict if it is to survive. The most influential model of the developmental process - certainly in terms of its impact upon texts aimed at practitioners - has been that of Bruce W. Tuckman (1965). While there are various differences concerning the number of stages and their names - many have adopted a version of Tuckman's model - forming, storming, norming and performing" http://www.infed.org/thinkers/tuckman.htm

fantastic article about agile and scrum. For those who think scrum is now the solution, the answer is: NO .... :) It doesn't matter which technology or methodology you use, you need the right people. http://www.industriallogic.com/blog/stop-using-story-points