Agile software development refers to a group of software development methodologies based on iterative development, where requirements and solutions evolve through collaboration between self-organizing cross-functional teams.
Agile
Key Points to ponder:
•Agile is a development methodology based on iterative and incremental approach.
•Agile software development has been widely seen as highly suited to environments which have small but expert project development team.
•In the Agile process, the leadership plays a vital role.
•The biggest advantage of agile is its flexibility as it quickly reacts to changes.
•Agile involves collaborations and face-to-face interactions between the members of various cross-functional teams.
•Agile can require lots of up-front development process and organizational change.
•Agile can require lots of up-front development process and organizational change.
•In this method, each step of development like requirements, analysis, design, are continually monitored during the lifecycle.
•Project head takes care of all the tasks in the agile method.
•Deliver and update the software on a regular basis.
•Deliver and update the software on a regular basis.
•In the Agile method, the priority is always to satisfy the customer by providing continuous delivery of valuable software.
•Working software is the most elementary measure of progress.
•It is best to have face-to-face communication, and techniques like these should be used to get as close to this goal as possible.
Following are Agile principles:
•Welcome changing requirements, even late in development. Agile processes allow change according to customer's competitive advantage.
•Business people and developers will work daily throughout the project.
•Attention to technical excellence and right design enhances agility
•Agile team, work on to become more effective, for that they adjust its behavior according to the project.
Scrum
Key points to ponder:
•Scrum is one of the implementations of agile methodology. In which incremental builds are delivered to the customer in every two to three weeks' time.
•Scrum is ideally used in the project where the requirement is rapidly changing.
•Scrum fosters a self-organizing, cross-functional team.
•Compared to Agile it is a more rigid method. So there is not much room for frequent changes.
•In Scrum, collaboration is achieved in daily stand up meeting with a fixed role assigned to scrum master, product owner, and team members.
•Not too many changes needed while implementing scrum process.
•In the scrum, after each sprint, a build is delivered to the client for their feedback.
•A demonstration of the functionality is provided at the end of every sprint. So that regular feedback can be taken before next sprint.
•There is no team leader, so the entire team addresses the issues or problems.
•Daily sprint meeting is conducted to review and feedback to decide future progress of the project.
•When the team is done with the current sprint activities, the next sprint can be planned.
•Design and execution can be innovative and experimental.
•Empirical Process Control is a core philosophy of Scrum based process.
•Working software is not an elementary measure.
•Scrum team focus to deliver maximum business value, from beginning early in the project and continuing throughout.
Following are scrum principles:
•Self-organization: This results in healthier shared ownership among the team members. It is also an innovative and creative environment which is conducive to growth.
•Collaboration: Collaboration is another essential principle which focuses on collaborative work. 1. awareness 2. articulation, and 3. appropriation. It also considers project management as a shared value-creation process with teams working together to offer the highest value.
•Time-boxing: This principle defines how time is a limiting constraint in Scrum method. An important element of time-boxed elements are Daily Sprint planning and Review Meetings.
•Iterative Development: This principle emphasizes how to manage changes better and build products which satisfy customer needs. It also defines the organization's responsibilities regarding iterative development.collaboration between self-organizing cross-functional teams.
Key Points to ponder:
•Agile is a development methodology based on iterative and incremental approach.
•Agile software development has been widely seen as highly suited to environments which have small but expert project development team.
•In the Agile process, the leadership plays a vital role.
•The biggest advantage of agile is its flexibility as it quickly reacts to changes.
•Agile involves collaborations and face-to-face interactions between the members of various cross-functional teams.
•Agile can require lots of up-front development process and organizational change.
•Agile can require lots of up-front development process and organizational change.
•In this method, each step of development like requirements, analysis, design, are continually monitored during the lifecycle.
•Project head takes care of all the tasks in the agile method.
•Deliver and update the software on a regular basis.
•Deliver and update the software on a regular basis.
•In the Agile method, the priority is always to satisfy the customer by providing continuous delivery of valuable software.
•Working software is the most elementary measure of progress.
•It is best to have face-to-face communication, and techniques like these should be used to get as close to this goal as possible.
Following are Agile principles:
•Welcome changing requirements, even late in development. Agile processes allow change according to customer's competitive advantage.
•Business people and developers will work daily throughout the project.
•Attention to technical excellence and right design enhances agility
•Agile team, work on to become more effective, for that they adjust its behavior according to the project.
Scrum
Key points to ponder:
•Scrum is one of the implementations of agile methodology. In which incremental builds are delivered to the customer in every two to three weeks' time.
•Scrum is ideally used in the project where the requirement is rapidly changing.
•Scrum fosters a self-organizing, cross-functional team.
•Compared to Agile it is a more rigid method. So there is not much room for frequent changes.
•In Scrum, collaboration is achieved in daily stand up meeting with a fixed role assigned to scrum master, product owner, and team members.
•Not too many changes needed while implementing scrum process.
•In the scrum, after each sprint, a build is delivered to the client for their feedback.
•A demonstration of the functionality is provided at the end of every sprint. So that regular feedback can be taken before next sprint.
•There is no team leader, so the entire team addresses the issues or problems.
•Daily sprint meeting is conducted to review and feedback to decide future progress of the project.
•When the team is done with the current sprint activities, the next sprint can be planned.
•Design and execution can be innovative and experimental.
•Empirical Process Control is a core philosophy of Scrum based process.
•Working software is not an elementary measure.
•Scrum team focus to deliver maximum business value, from beginning early in the project and continuing throughout.
Following are scrum principles:
•Self-organization: This results in healthier shared ownership among the team members. It is also an innovative and creative environment which is conducive to growth.
•Collaboration: Collaboration is another essential principle which focuses on collaborative work. 1. awareness 2. articulation, and 3. appropriation. It also considers project management as a shared value-creation process with teams working together to offer the highest value.
•Time-boxing: This principle defines how time is a limiting constraint in Scrum method. An important element of time-boxed elements are Daily Sprint planning and Review Meetings.
•Iterative Development: This principle emphasizes how to manage changes better and build products which satisfy customer needs. It also defines the organization's responsibilities regarding iterative development.collaboration between self-organizing cross-functional teams.
