Source: http://www.intelligentbee.com/blog/2015/02/20/should-you-do-scrum/
When conducting team projects, I have consistently felt that proceeding without a specific process is unproductive. Having been inspired by the Scrum-based development process of my friends at Somem Sinchon and Gangnam, I am reading a book to learn about Scrum and intend to apply it to my projects.
Daily Scrum Meeting
1. Do not book a separate meeting room.
2. Keep it standing and do not exceed 15 minutes.
3. 1) What have you done since the last daily Scrum meeting, 2) what do you plan to do before the next daily Scrum, 3) and what is blocking your work?
- During the Lineage 2 development team's Scrum -
"One must always be careful that Scrum or Agile does not become the team's goal itself."
"Common sense isn't common."
"To define Scrum in one sentence: 'Let’s exchange feedback earlier, more frequently, more abundantly, and more continuously.'"
The book states that Scrum is simple. It also notes that it is a method whose entire set of rules can be explained in less than 10 minutes. However, it warns that understanding the philosophy and the "why" of Scrum might take 10 days, and executing it properly might take over 10 weeks. Nevertheless, it maintains that Scrum is simple.
A Brief Introduction to Scrum
Source: http://upload.wikimedia.org/wikipedia/commons/thumb/5/58/Scrum_process.svg/2000px-Scrum_process.svg.png
Product Backlog
The Product Backlog is a list that catalogs everything the system needs to solve or include—that is, functionality, features, and technology. It is a list of all product requirements ordered by priority. The Product Backlog is never finalized; rather, it grows and evolves with the product. The highest-priority items in the Product Backlog are the most needed ones. Anyone can suggest items for the Product Backlog. Users, customers, the sales department, the marketing department, the customer service department, and the technical department can all submit items.
However, only the Product Owner can assign priorities to Product Backlog items. In effect, the Product Owner decides what gets developed first.
Sprint Backlog
Scrum teams are self-organizing and fully autonomous. They are restricted only by the standards and practices of the organization to which they belong and the Product Backlog they have chosen. It is entirely up to the development team to decide how to turn the chosen Product Backlog items into a product increment (I believe this refers to the Sprint Backlog). The team manages the list of tasks to be performed in that Sprint, which is the Sprint Backlog.
Sprint
Each Scrum team conducts development in 30-day iterative cycles called Sprints. During a Sprint, the team selects as much of the Product Backlog as they believe they can develop. At the end of every Sprint, a potentially shippable product with new functionality must be delivered. In reality, architecture and design are not completed in the first Sprint but gradually emerge over several Sprints.
Scrum Master
For Scrum to work well, the team must be voluntary and have conviction. During a Sprint, the manager, or Scrum Master, enforces the team's adherence to Scrum practices and helps the team make decisions or obtain necessary resources. During a Sprint, the team should not be interrupted or directed by anyone outside of the team.
Daily Scrum
The Scrum team holds a brief status meeting every day called the Daily Scrum. At the Daily Scrum, the manager reviews progress and identifies obstacles that need to be removed. The Daily Scrum is a great way to check the team's progress.
Ending a Sprint
The team gathers with the manager for a Sprint Review meeting to examine the Sprint Backlog developed during that period. After testing each Sprint Backlog (product increment), the manager usually organizes the Product Backlog so that the team's achievements can be utilized. The Product Backlog gains more meaning when viewed in light of the partially developed product. Once the Product Backlog is stabilized, the team selects the highest-priority items again for the next Sprint. This process is repeated until the Sprint is completed. This cyclic structure continues—evaluated based on empirical management costs, time, functionality, and quality—until it is determined that the product is potentially releasable. Along with this, a release Sprint is planned in preparation for the product release.
What is Scrum?
Scrum is straightforward.
Scrum clears away inappropriate and annoying management practices, leaving only the work itself.
Scrum leaves the team free to focus on their work.
Scrum provides developers with all the necessary management and control rights needed to focus on work and quickly produce high-quality products.
Source: http://www.codeproject.com/KB/architecture/scrum/diagram02.png
## References Scrum: Agile Methodologies to Maximize Team Productivity, Ken Schwaber