Agile model, Scrum
Agile:
# based on iterative and incremental development
# Customer satisfaction by rapid delivery of useful software
# Welcome changing requirements, even late in development
# Working software is delivered frequently
# Close, daily co-operation between business people and developers
# Face-to-face conversation is the best form of communication (co-location)
# Projects are built around motivated individuals, who should be trusted
# Self-organizing teams
# Regular adaptation to changing circumstances
# Agile methods break tasks into small increments with minimal planning, and do not directly involve long-term planning.
# based on iterative and incremental development
# Customer satisfaction by rapid delivery of useful software
# Welcome changing requirements, even late in development
# Working software is delivered frequently
# Close, daily co-operation between business people and developers
# Face-to-face conversation is the best form of communication (co-location)
# Projects are built around motivated individuals, who should be trusted
# Self-organizing teams
# Regular adaptation to changing circumstances
# Agile methods break tasks into small increments with minimal planning, and do not directly involve long-term planning.
# Iterations are short time frames (timeboxes) that typically last from one to four weeks. # Each iteration involves a team working through a full software development cycle including planning, requirements analysis, design, coding, unit testing, and acceptance testing when a working product is demonstrated to stakeholders.
# Stakeholders produce documentation as required.
# Team composition in an agile project is usually cross-functional and self-organizing without consideration for any existing corporate hierarchy or the corporate roles of team members.
# Team members normally take responsibility for tasks that deliver the functionality an iteration requires.
Scrum:
# iterative, incremental methodology for project management often seen in agile software development
# The main roles in Scrum are:
1. the “ScrumMaster”, who maintains the processes (typically in lieu of a project manager)
2. the “Product Owner”, who represents the stakeholders and the business
3. the “Team”, a cross-functional group of about 5-9 people who do the actual analysis, design, implementation, testing, etc.
# During each “sprint”, typically a two to four week period (with the length being decided by the team), the team creates a potentially shippable product increment (for example, working and tested software).
# The set of features that go into a sprint come from the product “backlog”, which is a prioritized set of high level requirements of work to be done. Which backlog items go into the sprint is determined during the sprint planning meeting. During this meeting, the Product Owner informs the team of the items in the product backlog that he or she wants completed. The team then determines how much of this they can commit to complete during the next sprint, and records this in the sprint backlog.[4] During a sprint, no one is allowed to change the sprint backlog, which means that the requirements are frozen for that sprint. Development is timeboxed such that the sprint must end on time; if requirements are not completed for any reason they are left out and returned to the product backlog. After a sprint is completed, the team demonstrates how to use the software.
# Represents a radically new approach for planning and managing software projects brings decision making authority to the level of operation properties and on certainties, scrum reduces defects , makes development process more efficient and reduces long term maintenance cost.[7]
* What have you done since yesterday?
* What are you planning to do today?
* Do you have any problems that would prevent you from accomplishing your goal? (It is the role of the ScrumMaster to facilitate resolution of these impediments, although the resolution should occur outside the Daily Scrum itself to keep it under 15 minutes.)
# Team composition in an agile project is usually cross-functional and self-organizing without consideration for any existing corporate hierarchy or the corporate roles of team members.
# Team members normally take responsibility for tasks that deliver the functionality an iteration requires.
Scrum:
# iterative, incremental methodology for project management often seen in agile software development
# The main roles in Scrum are:
1. the “ScrumMaster”, who maintains the processes (typically in lieu of a project manager)
2. the “Product Owner”, who represents the stakeholders and the business
3. the “Team”, a cross-functional group of about 5-9 people who do the actual analysis, design, implementation, testing, etc.
# During each “sprint”, typically a two to four week period (with the length being decided by the team), the team creates a potentially shippable product increment (for example, working and tested software).
# The set of features that go into a sprint come from the product “backlog”, which is a prioritized set of high level requirements of work to be done. Which backlog items go into the sprint is determined during the sprint planning meeting. During this meeting, the Product Owner informs the team of the items in the product backlog that he or she wants completed. The team then determines how much of this they can commit to complete during the next sprint, and records this in the sprint backlog.[4] During a sprint, no one is allowed to change the sprint backlog, which means that the requirements are frozen for that sprint. Development is timeboxed such that the sprint must end on time; if requirements are not completed for any reason they are left out and returned to the product backlog. After a sprint is completed, the team demonstrates how to use the software.
# Represents a radically new approach for planning and managing software projects brings decision making authority to the level of operation properties and on certainties, scrum reduces defects , makes development process more efficient and reduces long term maintenance cost.[7]
* What have you done since yesterday?
* What are you planning to do today?
* Do you have any problems that would prevent you from accomplishing your goal? (It is the role of the ScrumMaster to facilitate resolution of these impediments, although the resolution should occur outside the Daily Scrum itself to keep it under 15 minutes.)
No comments:
Post a Comment