Agile Methodology Overview

What is agile development?

Agile Development is a process that speeds the delivery of functionality to end users by segmenting a system into pieces for delivery, rather than delivering all of the system functionality in one large implementation.  The goal is to reduce the time between requests and delivery of Business Application Systems.  Pierson’s Agile training program will help you build a high performance development organization.

What are the agile methodology characteristics and principles?

  • Priority to satisfy the customer
  • Deliver functionality frequently
  • Iterations of 2 weeks to 3 months
  • Uses techniques such as time-boxing & dedicated teams
  • Team and collaboration- business users are involved throughout the project
  • Face-to-face conversations
  • Working software is the primary measure of progress
  • Attention to technical excellence and good design
  • Self-organizing teams

What is the difference between waterfall methodology vs. agile methodology?


What is the agile methodology SCRUM process?

To be successful, agile projects require a consistent management process. Below is a description of the various roles and essential tasks from planning to deployment.

Phase: Project Initiation
(Before the sprint starts)  The Product Owner gathers the project goals, product backlogs/priorities, team members and roles, communication plans and user stories.  The stories include:

  • Title
  • Description (As a <ROLE>, I want to <ACTION>, so I can <PURPOSE>.
  • Acceptance Test Criteria- implementation conditions must be true for the story to be considered complete.

Phase: Sprint Planning
The Scrum Master is responsible for establishing the length of the sprints (2 weeks), leading the team, defining the definition of “done” for each story, estimating the stories with the team and developing a project tracking tool. Sprint Planning Meeting should occur before each Sprint begins with the development team and business users to determine the items that should be developed next based on priority and dependencies.

Phase: Daily Scrums
Scrum Master is responsible for facilitating the 15 minute daily scrum meetings. They conduct the meetings with all team members to select stories for development, update the status of the stories, record blockers and calculate the time still required for the sprint completion for the burn down chart.

Phase: Sprint Retrospective
Scrum Master is responsible for reviewing the sprint status, discussing the changes required to improve the results for the next sprint and agreeing on the next sprint.

Phase: Demo
Product Owner is responsible for ensuring that a demo is performed, members of the team execute the demo and gather feedback. The team discusses the stories that will be completed in the upcoming sprint.

Phase: Product and Sprint Release
At the end of the sprint, the Product Owner communicates to the stakeholder community about the new feature being released and provides training for the new functionality.