Embrace Agile for Project Productivity

by Mar 30, 2022Services0 comments

Waterfall Methodology

The waterfall methodology uses a sequential or linear approach to software development. It is the most common methodology before Agile.


set of values, philosophy, and mindset.

Agile Methodology

  • The idea of Agile began in late 1990’s and it is formally launched in 2001.
  • Continuous incremental improvement through small and frequent releases.




Agile Manifesto

  • forms the foundation of Agile Movement
  • 17 people come up with core values and principles

4 Core Values

  1. Individuals and interactions over processes and tools
  2. Working software over comprehensive documentation
  3. Customer collaboration over contract negotiation
  4. Responding to changeover following a plan

12 Principles

  1. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
  2. Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage.
  3. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
  4. Business people and developers must work together daily throughout the project.
  5. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
  6. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
  7. Working software is the primary measure of progress.
  8. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
  9. Continuous attention to technical excellence and good design enhances agility.
  10. Simplicity–the art of maximizing the amount of work not done–is essential.
  11. The best architectures, requirements, and designs emerge from self-organizing teams.
  12. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.

3 terms to remember:

  1. Incremental – adding small changes
  2. Iterative – repetition of small sequences of operations or procedures iterative programming methods
  3. Continuous feedback – feedbacks from clients/user

Agile Key Concepts

  • User Stories
  • written from the perspective of client/ user
  • Should have 1 goal
  • Contains 4 major segments
  • Roles – actual human that interacts with the system
  • Action – what are we trying to achieve
  • Benefit – the thing that needs to be solved
  • Acceptance Criteria – set of predefined requirements that must be met to mark a user story complete


As a customer, I want shopping cart feature so that I can easily purchase item online.

Good user story should be








  • Epic

– large bodies of work that can be broken down into a number of smaller tasks

  • Initiative

-collection of epics that drive toward a common goal

  • Themes

-labels the epics and initiatives to understand what is the organization goals

  • Product Backlog

-lists and prioritizes task level details to execute a plan

-Dynamic: changes are possible

  • Product Roadmap

-shows detailed work and timeframe for each movement

-roadmap develop release plan and backlog

  • Agile Estimation/Planning Poker

-estimates the complexity of the user story/tasks

Minimum Viable Product

– basic or simplest version of the product

– must be viable


  • Units of work completed in a given timeframe


  • Changes is embraced
  • Fast, high quality delivery
  • Strong team interaction
  • Customers are heard
  • Continuous improvement


  • Planning can be less concrete
  • Team must be knowledgeable
  • Time commitment from developers is required
  • Documentation can be neglected


  • An incremental and iterative Agile project management framework that teams use to develop, deliver and sustain complex products.
  • Follows values and principles of Agile
  • Primarily used in software development


  • Agile is set of values and principles and Scrum is a way to implement it.

3 Pillars of Scrum

  • Transparency – clarity to what we should achieve
  • Inspection – regular monitoring
  • Adaptation – course correction to prevent further deviation


  • Stakeholders
  • Person external to Scrum team
  • Person from business who need to deliver the product
  • Provides constant feedback
  • Product Owner
  • Industry and Domain expert
  • Manages product backlog management
  • Scrum Master
  • Helps the Product Owner in maintaining the backlog, helps development team.
  • Facilitates Scrum Events
  • Development Team
  • Group of people who work on requirements and deliver a potentially releasable product
  • 3 to 9 members


  • Sprint Planning
  • Entire Scrum Team
  • 8 hrs is the limit
  • 2 Agendas: What is to be done and How it will be done
  • Daily Scrum Meeting
  • Entire Scrum Team
  • 15 minutes daily
  • Sprint Review
  • Entire Scrum Team and other Stakeholders
  • Talks about completed and not completed items
  • Discuss challenges and what to do next
  • Sprint Retrospective
  • Entire Scrum Team
  • Inspect the performance of the team


  • Product Backlog
  • Always evolving and never fixed
  • All the items in the software development project
  • Product Backlog Refinement
  • Changes – PO adds it to Backlog – PO and Dev’t Team add details
  • Sprint Backlog
  • List of which Development Team is currently working
  • Contains only the items of the Backlog specific to the current Sprint
  • Improvement is seen in Sprint Backlog
  • Increment
  • Final releasable product
  • Definition of ‘Done’


  • More transparency and project visibility
  • Increased team accountability
  • Easy to accommodate changes
  • Customers are heard


  • Risk of scope creep
  • Team requires experience and commitment
  • Poorly defined tasks can lead inaccuracies


Submit a Comment

Your email address will not be published. Required fields are marked *

Share This