Agile Manifesto

  • Firstly, Agile method process proposes incremental and iterative approach to software design while in Waterfall model,
    development of software flows sequentially from a start point to end point.
  • Agile process is broken into individual models that designers work on, while Waterfall process is not broken into modules.
  • In Agile process, customers have early and frequent opportunity to look at the product and make decisions and changes to the project.
    Waterfall process only allow customers to make changes at the end of the project.
  • Agile model is considered unstructured compared to waterfall which is more secured because they are plan oriented
  • Errors can be fixed at the middle of the project in Agile method while in Waterfall model, the project is being tested at the end and if
    error is found, the project has to start from the beginning.
  • Testers work with the developers in Agile model. Tester works differently with the developers in Waterfall Model
  • At the end of every sprint, user acceptance is performed in Agile model but User acceptance is performed at the end of the project in waterfall method
  • Scrum Master
    Master is responsible for setting up the team, sprint meeting and removes obstacles to progress.
  • Product owner
    The product owner creates product backlog, prioritizes the backlog and it is responsible for the delivery of the functionality at each iteration
  • Scrum Team
    Team manages its own work and organizes the work to complete the sprint or cycle.
  1. Eliminating Waste
  2. Amplifying learning
  3. Defer commitment (deciding as late as possible)
  4. Early delivery
  5. Empowering the team
  6. Building Integrity
  7. Optimize the whole
  • In Scrum technique, test must be broken down so that they can be completed with one sprint. In Kanban, No particular item is prescribed.
  • Scrum prescribes a prioritized product backlog while in Kanban, prioritization is optional.
  • Scrum team commits to a particular amount of work for the iteration, while commitment is optional in Kanban technique.
  • Burn down chart is prescribed in Scrum technique but No particular item size is prescribed in Kanban technique.
  • WIP is limited indirectly in Scrum Principle but directly in Kanban.

--

--

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store