Agile Software Development & Scrum
Content
Agile Software Development: Definition: 1. A group of software development methods based on iterative and incremental development. Its requirements and solutions evolve through collaboration between self-organizing, cross-functional teams. 2. It also helps to promote adaptive planning, evolutionary development and delivery, a time-boxed iterative way. 3.
Besides that, it encourages rapid and flexible response to change. It is a conceptual framework that promotes foreseen interactions throughout the development cycle.
4. Agile development methods are team-oriented because a single person will easy have do mistake, the mistakes maybe have not be fixed or corrected by ownself yet. This means that at the end of the product has poor quality. 5. If a team develops one product, errors made by one of the teammate are maybe discovered by other teammates to help them to fix and correct. Each of the members has their own specific role in a team. Some of them maybe too passive in doing thing or some of them plays the role as observer. So, agile methodologies were designed and work best with teams each other. This also able to improve the products and make the process efficient.
Manifesto of Agile Software Development: 1. Individuals and interactions over process and tools. 2. Working software over comprehensive documentation 3. Customer collaboration over contract negotiation 4. Responding to change over following a plan
Examples: Extreme Programming (XP)-most widely used agile process, originally preferred by Kent Beck. It uses an object oriented approach as its preferred development paradigm.
Scrum: Definition: 1. Another of agile method. This method is good for projects that have tight timelines, changing requirements and business criticality. 2. An iterative and incremental agile software development framework for managing software projects and products or application development. Its focus is on flexible, holistic product development strategy where a development team works as a unit to reach a common goal as opposed to a traditional, sequence approach. 3. Scrum contains a set of practices and three predefined roles. The project manager is usually become the Scrum master and maintain the processes. There also have the product owner, someone who represents the clients and a team of developers. So, it basically divided as scrum master, product owner and development team. 4. Meetings are held in very short duration and sometimes conducted without chairs. 5. A key principle of Scrum is its recognition that during a project, the customers can change their minds about what they want or need. 6. Development work is partitioned into packets. 7. Testing and documentation are done when the product is constructed.
Some main things in Scrum 1. Product -expects the team to bring the product or system to a potentially shippable state at the end of each Scrum sprint. 2. Scrum product backlog- complete list of the functionality that remains to added to products. The scrum product backlog is prioritized by the product owner so that the scrum team always works on the most suitable and valuable features first. So that, the products and process always will be more efficient. Most suitable product backlog is by described the functionality from the perspective of a user or clients. 3. Sprint planning meeting- the list of tasks the team needs to perform in order to deliver the functionality they committed to deliver during the sprint.
Besides that, it encourages rapid and flexible response to change. It is a conceptual framework that promotes foreseen interactions throughout the development cycle.
4. Agile development methods are team-oriented because a single person will easy have do mistake, the mistakes maybe have not be fixed or corrected by ownself yet. This means that at the end of the product has poor quality. 5. If a team develops one product, errors made by one of the teammate are maybe discovered by other teammates to help them to fix and correct. Each of the members has their own specific role in a team. Some of them maybe too passive in doing thing or some of them plays the role as observer. So, agile methodologies were designed and work best with teams each other. This also able to improve the products and make the process efficient.
Manifesto of Agile Software Development: 1. Individuals and interactions over process and tools. 2. Working software over comprehensive documentation 3. Customer collaboration over contract negotiation 4. Responding to change over following a plan
Examples: Extreme Programming (XP)-most widely used agile process, originally preferred by Kent Beck. It uses an object oriented approach as its preferred development paradigm.
Scrum: Definition: 1. Another of agile method. This method is good for projects that have tight timelines, changing requirements and business criticality. 2. An iterative and incremental agile software development framework for managing software projects and products or application development. Its focus is on flexible, holistic product development strategy where a development team works as a unit to reach a common goal as opposed to a traditional, sequence approach. 3. Scrum contains a set of practices and three predefined roles. The project manager is usually become the Scrum master and maintain the processes. There also have the product owner, someone who represents the clients and a team of developers. So, it basically divided as scrum master, product owner and development team. 4. Meetings are held in very short duration and sometimes conducted without chairs. 5. A key principle of Scrum is its recognition that during a project, the customers can change their minds about what they want or need. 6. Development work is partitioned into packets. 7. Testing and documentation are done when the product is constructed.
Some main things in Scrum 1. Product -expects the team to bring the product or system to a potentially shippable state at the end of each Scrum sprint. 2. Scrum product backlog- complete list of the functionality that remains to added to products. The scrum product backlog is prioritized by the product owner so that the scrum team always works on the most suitable and valuable features first. So that, the products and process always will be more efficient. Most suitable product backlog is by described the functionality from the perspective of a user or clients. 3. Sprint planning meeting- the list of tasks the team needs to perform in order to deliver the functionality they committed to deliver during the sprint.
