Scrum, a software development process developed by Hirotaka Takeuchi and Ikujiro Nonaka, in 1986, has become very popular as a generic product development framework in contemporary businesses. If you're looking into trying this methodology, here are a few important terms that you need to familiarize yourself with before you get started.
• Product owner-owner of the "Product" represents the voice of the customer in the development process. "The owner of the Product" is actually a member of the development team who analyzes customer opinions and stories, and adds them to product backlog for reference of the team.
• Scrum Master-the "Scrum Master" (or "Scrum Master") facilitates the whole process. He or she serves as the buffer between the team and keep the team focused on obstacles or distractions, the current tasks. A Scrum Master can also act as the owner of the Product as ned.
• Teams-the teams involved in this methodology that cross-functional skills that may have used to do the actual development work, including analysis, research, design and development, testing and even documentation. Scrum teams usually have 5-9 members in them, and are usually self-organized (Although managers/team leaders still under the authority of the Scrum Master).
• The backlog-backlogs are lists of tasks that the team must work. There are two types of payments: the product – behind, which the General list of what needs to be done during the whole process; and the sprint backlog, which is a list of tasks that need to be completed during the sprint.
• Sprint-Sprints in scrum methodology are periods in which the actual action and development takes place. They typically last for 2-4 weeks, and the tasks to be performed during each sprint are based on the sprint backlog.
• Sprint burn down chart-this is a checklist of tasks that is updated on a daily basis during a sprint. It is displayed in such a way that all the team members can easily update and maintain and see what is left to be completed.
• Daily scrum-short, daily meetings that arise during a sprint. During this meeting, the team describes what the previous day, what should be done, problems or obstacles that hamper the was achieved and progress.
• Sprint retrospective-a longer meeting that occurs at the end of a sprint, in which team members get together to discuss the previous sprint and how the next one can be further improved.
For more information about product development methodologies such as scrum and agile, Scrum!
{ 0 komentar... Views All / Send Comment! }
Posting Komentar