1By: Mohamed Saad
2012 – Dec
 Development Methodologies
 What is Agile?
 Why Agile?
 Agile Methods
 SCRUM
› ROLE S
› Sprint
› Me e t ings
› Art if...
 Predictive methods:
› Contrast, focus on analyzing and planning the
future in detail and cater for known risks.
› Projec...
 Agile software development is a group of software
development methods based on iterative and
incremental development.
 ...
 Individuals and interactions over processes
and tools.
 Working software over comprehensive
documentation.
 Customer c...
 Promote development, teamwork, collaboration, and
process adaptability throughout the life-cycle of the project.
 Agile...
 Team composition in an agile project is usually cross-
functional and self-organizing, without consideration
for any exi...
 Scrum
 Extreme Programming (XP)
 Crystal Clear
 Agile Modeling
 Agile Unified Process (AUP)
 Dynamic Systems Develo...
 What is SCRUM?
 Roles
 Sprint
 Meetings
 Tools
9
 Scrum is an iterative and incremental agile
software development framework for managing
software projects and product or...
 Core roles
› Product Owner
› Development Team
› Scrum Master
 Ancillary roles
› Stakeholders
› Managers
11
 Product Owner
› Represents the stakeholders and is the voice of
the customer. He or she is accountable for
ensuring that...
 Development Team
› The Development Team is responsible for
delivering potentially shippable product
increments at the en...
 Scrum Master
› Accountable for removing difficulties for the
ability of the team to deliver the sprint
goal/deliverables...
 Stakeholders
› Are the customers, vendors.
› They are only directly involved in the process
during the sprint reviews.
...
16
 A sprint is the basic unit of development in Scrum.
 Sprints last between one week and one month.
 Each sprint is prec...
 If requirements are not completed for any reason
they are left out and returned to the product
backlog.
 If requirement...
 Daily Scrum
› Guidelines:
 All members of the development Team come prepared
with the updates for the meeting.
 The me...
› Main points:
 What have you done since yesterday?
 What are you planning to do today?
 Any impediments/stumbling bloc...
 Backlog grooming: storytime
› This is the process of estimating the existing backlog using
effort/points
› Refining the ...
 Scrum of Scrums
› Working With Multiple Scrum Teams
› Each day normally after the Daily Scrum.
› Guidelines:
 Allow clu...
› Main Points:
 What has your team done since we last met?
 What will your team do before we meet
again?
 Is anything s...
 Sprint planning meeting
› At the beginning of the sprint cycle.
› Guidelines:
 Eight-hour time limit
 (1st four hours)...
› Main Points:
 Select what work is to be done.
 Prepare the Sprint Backlog that details the
time it will take to do tha...
 Sprint review meeting
› At the end of a sprint cycle.
› Guidelines:
 Four-hour time limit.
› Main Points:
 Review the ...
 Sprint retrospective
› At the end of a sprint cycle.
› Guidelines:
 Three-hour time limit.
 This meeting is facilitate...
 Product Backlog
› Is an ordered list of "requirements" that is maintained for a
product.
› It contains Product Backlog I...
 Sprint Backlog
› Is the list of work the Development Team must address
during the next sprint.
› Is derived by selecting...
 Sprint Backlog
30
 Increment
› Is the sum of all the Product Backlog Items completed
during a sprint and all previous sprints.
 Burn down
...
 Burn down
32
33
 http://en.wikipedia.org/wiki/Agile_software
_development
 Agile For Dummies, CA Technologies Edition
 The Art of Agile...
Upcoming SlideShare
Loading in …5
×

Introduction to agile and scrum

363 views

Published on

Introduction to agile and scrum

Published in: Real Estate, Technology, Business
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
363
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
4
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Introduction to agile and scrum

  1. 1. 1By: Mohamed Saad 2012 – Dec
  2. 2.  Development Methodologies  What is Agile?  Why Agile?  Agile Methods  SCRUM › ROLE S › Sprint › Me e t ings › Art ifact s  References. 2
  3. 3.  Predictive methods: › Contrast, focus on analyzing and planning the future in detail and cater for known risks. › Project may have difficulty changing direction.  Adaptive methods (e.g. Agile): › Adaptive methods focus on adapting quickly to changing realities. › An adaptive team will have difficulty describing exactly what will happen in the future. 3
  4. 4.  Agile software development is a group of software development methods based on iterative and incremental development.  Requirements and solutions evolve through collaboration between self-organizing, cross- functional teams.  It promotes adaptive planning, evolutionary development and delivery, a time-boxed iterative approach.  Encourages rapid and flexible response to change. 4
  5. 5.  Individuals and interactions over processes and tools.  Working software over comprehensive documentation.  Customer collaboration over contract negotiation.  Responding to change over following a plan. 5
  6. 6.  Promote development, teamwork, collaboration, and process adaptability throughout the life-cycle of the project.  Agile methods break tasks into small increments with minimal planning and do not directly involve long-term planning.  Iterations are short time frames (timeboxes) that typically last from one to four weeks.  Each iteration involves a cross functional team working in all functions: planning, requirements analysis, design, coding, unit testing, and acceptance testing.  At the end of the iteration a working product is demonstrated to stakeholders. 6
  7. 7.  Team composition in an agile project is usually cross- functional and self-organizing, without consideration for any existing corporate hierarchy or the corporate roles of team members.  Agile methods emphasize face-to-face communication over written documents.  Each agile team will contain a customer representative.  Daily face-to-face communication among team members and customer representative and any interested stakeholders as observers.  Agile development emphasizes working software as the primary measure of progress. 7
  8. 8.  Scrum  Extreme Programming (XP)  Crystal Clear  Agile Modeling  Agile Unified Process (AUP)  Dynamic Systems Development Method (DSDM)  Feature Driven Development (FDD)  GSD  Kanban (development)  Lean software development  Velocity tracking 8
  9. 9.  What is SCRUM?  Roles  Sprint  Meetings  Tools 9
  10. 10.  Scrum is an iterative and incremental agile software development framework for managing software projects and product or application development.  Scrum focuses on project management where it is difficult to plan ahead.  Mechanisms of empirical process control, where feedback loops that constitute the core management technique are used as opposed to traditional command-and-control oriented management. 10
  11. 11.  Core roles › Product Owner › Development Team › Scrum Master  Ancillary roles › Stakeholders › Managers 11
  12. 12.  Product Owner › Represents the stakeholders and is the voice of the customer. He or she is accountable for ensuring that the team delivers value to the business. › The Product Owner writes customer-centric items (typically user stories), prioritizes them and adds them to the product backlog and adds them to the product backlog. › Scrum teams should have one Product Owner. 12
  13. 13.  Development Team › The Development Team is responsible for delivering potentially shippable product increments at the end of each Sprint. › Development Team is made up of 3–9 people with cross-functional skills who do the actual work (analyse, design, develop, test, technical communication, document, etc.) › Development Team in Scrum is self-organizing. 13
  14. 14.  Scrum Master › Accountable for removing difficulties for the ability of the team to deliver the sprint goal/deliverables. › Scrum Master is not the team leader. › Scrum Master ensures that the Scrum process is used as intended. › It is recommended that this role not be combined with that of Scrum Master. 14
  15. 15.  Stakeholders › Are the customers, vendors. › They are only directly involved in the process during the sprint reviews.  Managers › People who control the environment. 15
  16. 16. 16
  17. 17.  A sprint is the basic unit of development in Scrum.  Sprints last between one week and one month.  Each sprint is preceded by a planning meeting.  During each sprint, the team creates finished portions of a product.  The Sprint backlog come from the product backlog.  Development is timeboxed such that the sprint must end on time. If requirements are not completed for any reason they are left out and returned to the product backlog. 17
  18. 18.  If requirements are not completed for any reason they are left out and returned to the product backlog.  If requirements are not completed for any reason they are left out and returned to the product backlog.  A key principle of Scrum is its recognition that during a project the customers can change their minds about what they want and need. 18
  19. 19.  Daily Scrum › Guidelines:  All members of the development Team come prepared with the updates for the meeting.  The meeting starts precisely on time even if some development team members are missing.  The meeting should happen at the same location and same time every day.  The meeting length is set (timeboxed) to 15 minutes.  All are welcome, but normally only the core roles speak. 19
  20. 20. › Main points:  What have you done since yesterday?  What are you planning to do today?  Any impediments/stumbling blocks? 20
  21. 21.  Backlog grooming: storytime › This is the process of estimating the existing backlog using effort/points › Refining the acceptance criteria for individual stories › Breaking larger stories into smaller stories. › Guidelines:  Meetings should not be longer than an hour  Meeting does not include breaking stories into tasks  The team can decide how many meetings are needed per week. 21
  22. 22.  Scrum of Scrums › Working With Multiple Scrum Teams › Each day normally after the Daily Scrum. › Guidelines:  Allow clusters of teams to discuss their work, focusing especially on areas of overlap and integration.  A designated person from each team attends. 22
  23. 23. › Main Points:  What has your team done since we last met?  What will your team do before we meet again?  Is anything slowing your team down or getting in their way?  Are you about to put something in another team’s way? 23
  24. 24.  Sprint planning meeting › At the beginning of the sprint cycle. › Guidelines:  Eight-hour time limit  (1st four hours) Entire team: dialog for prioritizing the Product Backlog.  (2nd four hours) Development Team: hashing out a plan for the Sprint, resulting in the Sprint Backlog. 24
  25. 25. › Main Points:  Select what work is to be done.  Prepare the Sprint Backlog that details the time it will take to do that work, with the entire team.  Identify and communicate how much of the work is likely to be done during the current sprint. 25
  26. 26.  Sprint review meeting › At the end of a sprint cycle. › Guidelines:  Four-hour time limit. › Main Points:  Review the work that was completed and not completed.  Present the completed work to the stakeholders.  Incomplete work cannot be demonstrated 26
  27. 27.  Sprint retrospective › At the end of a sprint cycle. › Guidelines:  Three-hour time limit.  This meeting is facilitated by the Scrum Master. › Main Points:  What went well during the sprint?  What could be improved in the next sprint? 27
  28. 28.  Product Backlog › Is an ordered list of "requirements" that is maintained for a product. › It contains Product Backlog Items that are ordered by the Product Owner. › The features added to the backlog are commonly written in story format. › The product backlog contains rough estimates of both business value and development effort. › Business values are the responsibility of the Product Owner and estimated efforts are determined by the Development Team. 28
  29. 29.  Sprint Backlog › Is the list of work the Development Team must address during the next sprint. › Is derived by selecting stories/features from the top of the product backlog until the Development Team feels it has enough work to fill the sprint. › Development Team should keep in mind the velocity of its previous Sprints. › The stories/features are broken down into tasks by the Development Team. › Development Team understands exactly what to do, and potentially, anyone can pick a task from the list. 29
  30. 30.  Sprint Backlog 30
  31. 31.  Increment › Is the sum of all the Product Backlog Items completed during a sprint and all previous sprints.  Burn down › Is a publicly displayed chart showing remaining work in the sprint backlog. › Updated every day. › It gives a simple view of the sprint progress. › Types of burndown:  release burndown chart:  alternative release burndown chart. 31
  32. 32.  Burn down 32
  33. 33. 33
  34. 34.  http://en.wikipedia.org/wiki/Agile_software _development  Agile For Dummies, CA Technologies Edition  The Art of Agile Development 34

×