Agile Scrum Methodology

By. Sirisha.D

Contents
Introduction to Agile Model. Agile Manifesto & Principles.

Methodologies in Agile Model.

Scrum Methodology Scrum Characteristics Scrum Roles & Responsibilities Scrum Activities & Artifacts Scrum Life Cycle Advantages Disadvantages/Challenges Conclusion

Agile Model and Manifesto

Agile - ease of movement, nimble, active, lightness.

Agile Model:

Lightweight Software development Model.

Requirements and solutions evolve through collaboration between self-organizing & cross functional teams.

A Conceptual framework that promotes adaptive planning, evolutionary development and delivery, a

time-boxed iterative approach.

Agile Manifesto: Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan

That is, while there is value in the items on the right, we value the items on the left more.

Agile Principles
Twelve principles underlie the Agile Manifesto: Customer Satisfaction by rapid delivery of useful software Welcome Changing Requirements, even late in development Working Software is delivered frequently (weeks rather than months) Working Software is the principal measure of progress Sustainable Development, able to maintain a constant pace

Daily Co-operation between business people and developers

Face-to-Face Conversation is the best form of communication (co-location) Projects are built around Motivated Individuals, who should be trusted Continuous attention to Technical Excellence and Good Design

Simplicity - The art of maximizing the amount of work not done - is essential
Self-organizing teams Regular Adaptation to changing circumstances

Agile Methodologies
Well-known agile software development methods include:

AGI LE

Dynamic Systems Development Method (DSDM) Extreme Programming (XP) Scrum

Agile Unified Process (AUP) Feature Driven Development (FDD)

Scrum Methodology
Iterative/incremental agile software development method. Agile process that allows us to focus on delivering the highest business value in the shortest time. The business sets the priorities. Teams self-organize to determine the best way to deliver the highest priority features. It allows us to rapidly and repeatedly inspect actual working software (every two weeks to one month).
Milestone Inch Pebbles

Scrum Characteristics

Characteristics: Dynamic & Flexible Time Bound approach Collaboration Small Team Size (5-10 resources) Involves Customer Involvement the process Documentation is not given mandatory Own Individual and Collective responsibility. Product progresses in a series of month-long sprints Requirements are captured as items in a list of Product Backlog

Scrum Roles and Responsibilities

Scrum Team includes: Product Owner Scrum Master Team Members (Developers, Testers, Technical Writers)

Product Owner: Define the features of the Product, Works with business stakeholders to compile and prioritize user stories/requirements according to market value Decide on release date and content Be responsible for the profitability of the product (ROI) Guides stakeholders in how to vertically slice their projects into small but shippable deliverables. Extracts and documents user acceptance criteria from the stakeholders. Adjust features and priority every iteration, as needed. Accept or reject work results

Continued

Scrum Master: Represents management to the project Responsible for enacting Scrum values and practices Removes impediments Ensure that the team is fully functional and productive Enable close cooperation across all roles and functions Shield the team from external interferences Monitors the process The driver of the Team Responsible for the team functioning

Continued
Activities of Scrum Master: Meetings Artifacts Coaching Working with the Product Owner

Scrum Team Members: Typically 5-10 members. Team Members are called as Pigs; Stake holders, Other members, Management are called as Chickens Cross-Functional, Self Organizing, Fully dedicated. Members should be full time (exceptions: System Admin, DB Admin). Makes decisions collaboratively. Collectively responsible for sprint delivery. Team involvement in all phases. Equal treatment and respect all.

Scrum Activities and Artifacts

Activities: Sprint Planning Meeting Sprint Daily Scrum Meeting Sprint Review & Retrospective

Artifacts: Product Backlog Sprint Backlog Burn down Chart

Continued

Sprint Planning Meeting:

Phase1: Inputs from Product Backlog Determining the Sprint Goal. Participants: Product Owner, Scrum Master, Scrum Team

Phase 2: Participants: Scrum Master, Scrum Team Meeting before the begin of the Project Creating Sprint Backlog

Continued

Continued
Sprint Backlog: A subset of Product Backlog Items, which define the work for a Sprint Is created only by Team members Each Item has its own status Should be updated every day

Sprint:
A sprint is the basic unit of development in Scrum. Sprints last between one week and one month Time Bound, Effort of constant length, pace. During each sprint, the team creates finished portions of a product

Continued
Rules: No changes during sprint cycle. Membership can change only between sprints. No outside influence can interfere with the Scrum team during the Sprint. Requirements can be changed and re-prioritized before starting Sprint Cycle. Scrum team takes the Sprint Goal and decides what tasks are necessary. Team self-organizes around how theyll meet the Sprint Goal. Team adds new tasks whenever they need to in order to meet the Sprint Goal. Team can remove unnecessary tasks, Sprint Backlog can only be updated by the team. Estimates are updated whenever theres new information. Daily Scrum Meeting.

Continued
Daily Scrum Meeting: 15 minutes stand up meeting led by the scrum master Team meeting every day at the same time in the same place. All members are invited; Only team members speak. Three questions: 1. What did you do yesterday 2. What will you do today? 3. What obstacles are in your way? Following Activities: Team members update the Sprint Backlog with hours remaining for tasks that theyve worked on Scrum Master adds up the hours remaining and plots it on the Burn down Chart

Is a meeting in which team members make commitments to each other and to the Scrum Master in front of peers. Is a good way for a Scrum Master to track the progress of the Team

Continued

Sprint Review and Retrospective

Sprint Review:

Team presents what it accomplished during the sprint. Participants: Customers, Team Members, Product Owner, Scrum Master, Manager..etc.

Typically takes the form of a demo of new features

Acceptance Criteria. 4-hour time limit.

Sprint Review and Retrospective

Sprint Retrospective:

Participants: Team Members, Product Owner, Scrum Master. All team members reflect on the past sprint
Two main questions are asked in the sprint retrospective: What went well during the sprint? What could be improved in the next sprint?

Three-hour time limit This meeting is facilitated by the Scrum Master Make continuous process improvements

Product Backlog

Sprint Backlog

Hours of work remaining in each day of sprint Initial Backlog Item Design Business Logic Design User Interface Enable all users to place Implement Back-End Code book in shopping cart Complete Unit Testing Complete Regression Testing Task Task Owner Sanjay Tracy Sarah Philip Sam Day Day Day Day Day Day Day Day Estimate 1 2 3 4 5 6 7 8 4 5 7 3 4

Write Documentation
Upgrade Transaction Merge DCP Code and complete layer -level tests Processing Module

Thomas Sanjay
Tracy Sarah Total

3 5
4 3 38

Burn down Chart

Scrum Life Cycle

Advantages
Increased Productivity Good Return on Investment (ROI) Improved Communication Completely developed and tested features in short iterations Adaptive and ability to respond to unpredictable requirements. Flexibility Collective Ownership Trust between customers and developers is established and a positive culture is created in which everyone expects the project to succeed. The whole team will have visibility of everything.

Disadvantages/Challenges

Expensive

Training is required
They may not implement the whole process Difficult to prioritize the requirements in case of diverse set of Stake Holders Difficult to coordinate and communicate when team members are present in different locations Requires customer involvement on regular basis.

Conclusion

Scrum is a efficient agile process that allows us to focus on delivering the highest business value in the
shortest time.

Effective Process when requirements are frequently changing and is unpredictable Empirical Approach. Customer satisfaction.

Any Questions