For other uses, see Scrum. Scrum is an agile software development method for project management. Look up scrum in Wiktionary, the free dictionary. ...
Image File history File links This is a lossless scalable vector image. ...
Image File history File links This is a lossless scalable vector image. ...
Agile software development is a conceptual framework for undertaking software engineering projects that embraces and promotes evolutionary change throughout the entire life-cycle of the project. ...
Project Management is the discipline of organizing and managing resources (e. ...
Scrum background The approach was first described by Takeuchi and Nonaka in "The New New Product Development Game" (Harvard Business Review, Jan-Feb 1986). They noted that projects using small, cross-functional teams historically produce the best results, and likened these high-performing teams to the scrum formation in Rugby. In 1991, DeGrace and Stahl, in "Wicked Problems, Righteous Solutions" referred to this approach as Scrum. Ken Schwaber used an approach that led to Scrum at his company, Advanced Development Methods, in the early 1990's. At the same time, Jeff Sutherland, John Scumniotales, and Jeff McKenna developed a similar approach at Easel Corporation and were the first to call it Scrum. Jeff Sutherland and Ken jointly presented a paper describing Scrum at OOPSLA '96 in Austin, its first public appearance. Ken and Jeff collaborated during the following years to merge the above writings, their experiences, and industry best practices into what is now known as Scrum. A rugby union scrum. ...
For other uses, see Rugby (disambiguation). ...
Ken Schwaber is the owner of the scrummaster trademark, a course in Scrum software development process. ...
Jeff Sutherland, Ph. ...
OOPSLA (Object-Oriented Programming, Systems, Languages & Applications) is an annual ACM conference. ...
Although Scrum was intended to be for management of software development projects, it can be used in running maintenance teams, or as a program management approach: Scrum of Scrums.
Characteristics of Scrum - A product backlog of prioritized work to be done;
- Completion of a fixed set of backlog items in a series of short iterations or sprints;
- A brief daily meeting or scrum, at which progress is explained, upcoming work is described and impediments are raised.
- A brief sprint planning session in which the backlog items for the sprint will be defined.
- A brief sprint retrospective, at which all team members reflect about the past sprint.
Scrum is facilitated by a ScrumMaster, whose primary job is to remove impediments to the ability of the team to deliver the sprint goal. The ScrumMaster is not the leader of the team (as they are self-organising) but acts as a buffer between the team and any distracting influences.
Scrum enables the creation of self-organizing teams by encouraging co-location of all team members, and verbal communication across all team members and disciplines that are involved in the project.
A key principle of Scrum is its recognition that fundamentally empirical challenges cannot be addressed successfully in a traditional predictive or planned manner. As such, Scrum adopts an empirical approach – accepting that the problem cannot be fully understood or defined, focusing instead on maximizing the team's ability to deliver quickly and respond to emerging requirements. A central concept in science and the scientific method is that all evidence must be empirical, or empirically based, that is, dependent on evidence or consequences that are observable by the senses. ...
Adaptive project management Following are some practices for the Scrum: - Customers become a part of the development team. (i.e., Customer must be genuinely interested in the output.) – VOC – In SDLC parlance, validate what you have planned to develop.
- Frequent intermediate deliveries with working functionality. – Incremental development and releases (may be internal only) – providing you an opportunity to validate and verify at shorter intervals rather than only at the end; thereby, providing you time to fix, and reducing the cost to fix.
- Frequent risk and mitigation plans developed by the development team itself. – Risk Mitigation, Monitoring and Management (risk analysis) at every stage and with genuinity – Make it live, and continuous activity.
- A daily status discussion (Standup meetings) asking each team member:
- What have you done since yesterday? (accomplishments)
- What are you planning to do by tomorrow? (to be accomplished)
- Do you have any problems preventing you from accomplishing your goal? (issues/concerns/risks)
- Transparency in planning and module development – Let everyone know who is accountable for what and by when.
- Frequent stakeholder meetings to monitor progress – Balanced (Delivery, Customer, Employee, Process) Dashboard updates – Stakeholders' update – You have to have Advance Warning Mechanism, i.e. visibility to potential slippage / deviation ahead of time.
- No problems are swept under the carpet. No one is penalized for recognizing or describing any unforeseen problem.
- Workplaces and working hours must be energized. – "Working more hours" does not necessarily mean "producing more output."
It has been suggested that this article or section be merged with System Development Life Cycle. ...
A stand-up in agile methods is a daily team meeting held to provide a status update to the team members. ...
Scheduling daily status discussions A popular time for the daily status discussion is after the lunch break. Doing it in the morning may be troublesome especially if the team is working in a company using flextime. These status discussions don't take long, so one way is to do standup meetings where the team meets in front of a whiteboard. Because people tend to get tired after lunch, having a lively standup meeting at that time may keep their energy up. Because everybody has already been working that day, their minds are focused on the job and not on their personal issues. Flextime (or flexitime Flexi-time) is a variable work schedule, in contrast to traditional work arrangements requiring employees to work a standard 9am to 5pm day. ...
Solo Scrum Scrum is based on small teams. It enhances communication between team members. Nevertheless, there is a huge amount of software that is being developed by solo programmers. A software system being built by a single programmer can still benefit from some of the Scrum principles such as: a product backlog, a sprint backlog, a sprint and a sprint retrospective. Solo Scrum is an adapted version of Scrum for use by solo programmers.
Scrum terminology Scrum Master: The person or persons in charge of the tracking and the daily updates for the scrum (equivalent to a project manager). Sometimes referred to as a Scrum Facilitator.
Scrum Team: A cross-functional team (developers, B.A.s, DBAs, and testers) responsible for developing the product.
Product Owner: The person responsible for maintaining the Product Backlog via continuous interaction with Clients and Stakeholders.
Story: A customer focused description of valued functionality.
Product Backlog: The stories to be completed.
Sprint: A time period (usually 2 to 4 weeks) in which development occurs on a set of stories that the team has committed to.
Burn Down Chart: Daily progress for a sprint over the sprint's length.
Other non-professional Scrum Terms Scrum Toon: A cartoon used to explain scrum and its intricacies on teams where scrum is first implemented.
Pigs: Those who are members of the Scrum Team committed to the tasks (developers, B.A.s, DBAs, and testers).
Chickens: Those who are involved but do not have tasks (Project Owners, Scrum Masters, Stakeholders, Clients, etc...).
Pig & Chicken are used to describe the relationship between all persons associated with a product. The names, while strange, are derived from an allegory about the commitment involved in creating a ham and egg breakfast: the chicken is involved, but the pig is committed.
Books - Agile Project Management with Scrum, Ken Schwaber, Microsoft Press, January 2004, 163pp, ISBN 0-7356-1993-X
- Agile Software Development with Scrum, Ken Schwaber and Mike Beedle, Prentice Hall, 2001, 150pp, ISBN 0130676349
- Scrum and XP from the Trenches, Henrik Kniberg, Version 2.2, 24 April 2007 [1]
Microsoft Press is the publishing arm of Microsoft, usually releasing books dealing with various current Microsoft technologies. ...
Year 2004 (MMIV) was a leap year starting on Thursday of the Gregorian calendar. ...
Pearson can mean Pearson PLC the media conglomerate. ...
Year 2001 (MMI) was a common year starting on Monday (link displays the 2001 Gregorian calendar). ...
is the 114th day of the year (115th in leap years) in the Gregorian calendar. ...
Year 2007 (MMVII) is the current year, a common year starting on Monday of the Gregorian calendar and the AD/CE era. ...
Challenges to Adoption of Scrum Many organizations are resistant to Scrum and other Agile methodologies. The power of the ideas and the associated change management effort impact how effectively companies can adopt Scrum. The increased transparency experienced from using this methodology forces accountability, responsibility, prioritization discussions, trade-offs, and often scope reduction. Scrum requires that managers behave differently than in the past. Instead of reviewing status reports, managers should attend Sprint reviews and retrospectives. Instead of waiting for team members to prepare and present updates, management should go to the project room and see the project's task board and burn down chart.
One wiki writer suggests that Scrum's adaptability allows it to be introduced "stealthily". E.g. using three steps:
- Schedule a demo of the software with the customer/client a month from now
- As a team, take a month to get your software ready for the demo – actually functioning, not just screen shots
- At the demo, get feedback and use it to guide the next month's development work
While this might work, it does not address the fundamental changes in behavior that the project manager, the team, and management should commit to and undertake. Stealth mode implementations often cause "organizational antibodies" to form that will resist and undermine the changes.
Disadvantages Any and all methodologies have their pros and cons.
Scrum gives much power to Scrum Team, so having inexperienced or heterogeneous team brings in more uncertainty. However, since a Sprint consists of a rather small amount of work, the Scrum Master can react to any skill related problem quite fast.
The Product Owner defines priorization by using the Product Backlog, so in a sprint planning session the most important features will be selected. This may cause extra work to be done, because quite often there are critical - but somehow unnoticed modules or services to be implemented. The Scrum Team must handle situation like this with care and build a stub and may be reduce some functionality for current sprint.
References - ^ http://www.crisp.se/henrik.kniberg/ScrumAndXpFromTheTrenches.pdf
Sources is the 74th day of the year (75th in leap years) in the Gregorian calendar. ...
Year 2007 (MMVII) is the current year, a common year starting on Monday of the Gregorian calendar and the AD/CE era. ...
is the 227th day of the year (228th in leap years) in the Gregorian calendar. ...
Year 2006 (MMVI) was a common year starting on Sunday of the Gregorian calendar. ...
is the 227th day of the year (228th in leap years) in the Gregorian calendar. ...
Year 2006 (MMVI) was a common year starting on Sunday of the Gregorian calendar. ...
See also This is an incomplete list of approaches, styles, or philosophies in software development. ...
A user story is a software system requirement formulated as one or two sentences in the everyday language of the user. ...
Other Agile methods Dynamic Systems Development Method is a Rapid Application Development method concerned mainly with the development of computerised Information Systems. ...
Feature Drive Development (FDD) is an iterative and incremental software development process. ...
Extreme Programming (or XP) is a software engineering methodology, the most prominent of several agile software development methodologies, prescribing a set of daily stakeholder practices that embody and encourage particular XP values (below). ...
External links
Scrum in general project management |
Feeds |
Contact