• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Introduction to agile and scrum
 

Introduction to agile and scrum

on

  • 312 views

Introduction to agile and scrum

Introduction to agile and scrum

Statistics

Views

Total Views
312
Views on SlideShare
312
Embed Views
0

Actions

Likes
1
Downloads
0
Comments
0

0 Embeds 0

No embeds

Accessibility

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Introduction to agile and scrum Introduction to agile and scrum Presentation Transcript

    • 1
    •  Development Methodologies What is Agile? Why Agile? Agile Methods SCRUM› ROLES› Sprint› Meetings› Artifacts References.2
    •  Predictive methods:› Contrast, focus on analyzing and planningthe future in detail and cater for known risks.› Project may have difficulty changingdirection. Adaptive methods (e.g. Agile):› Adaptive methods focus on adaptingquickly to changing realities.› An adaptive team will have difficultydescribing exactly what will happen in thefuture.3
    •  Agile software development is a group ofsoftware development methods based oniterative and incremental development. Requirements and solutions evolve throughcollaboration between self-organizing, cross-functional teams. It promotes adaptive planning, evolutionarydevelopment and delivery, a time-boxediterative approach. Encourages rapid and flexible response tochange.4
    •  Individuals and interactions overprocesses and tools. Working software over comprehensivedocumentation. Customer collaboration over contractnegotiation. Responding to change over following aplan.5
    •  Promote development, teamwork, collaboration, andprocess adaptability throughout the life-cycle of theproject. Agile methods break tasks into small increments withminimal planning and do not directly involve long-term planning. Iterations are short time frames (timeboxes) thattypically last from one to four weeks. Each iteration involves a cross functional teamworking in all functions: planning, requirementsanalysis, design, coding, unit testing, andacceptance testing. At the end of the iteration a working product isdemonstrated to stakeholders.6
    •  Team composition in an agile project is usually cross-functional and self-organizing, without considerationfor any existing corporate hierarchy or the corporateroles of team members. Agile methods emphasize face-to-facecommunication over written documents. Each agile team will contain a customerrepresentative. Daily face-to-face communication among teammembers and customer representative and anyinterested stakeholders as observers. Agile development emphasizes working software asthe primary measure of progress.7
    •  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 tracking8
    •  What is SCRUM? Roles Sprint Meetings Tools9
    •  Scrum is an iterative and incremental agilesoftware development framework formanaging software projects and product orapplication development. Scrum focuses on project managementwhere it is difficult to plan ahead. Mechanisms of empirical process control,where feedback loops that constitute thecore management technique are used asopposed to traditional command-and-control oriented management.10
    •  Core roles› Product Owner› Development Team› Scrum Master Ancillary roles› Stakeholders› Managers11
    •  Product Owner› Represents the stakeholders and is the voiceof the customer. He or she is accountable forensuring that the team delivers value to thebusiness.› The Product Owner writes customer-centricitems (typically user stories), prioritizes themand adds them to the product backlog andadds them to the product backlog.› Scrum teams should have one ProductOwner.12
    •  Development Team› The Development Team is responsible fordelivering potentially shippable productincrements at the end of each Sprint.› Development Team is made up of 3–9people with cross-functional skills who do theactual work(analyse, design, develop, test, technicalcommunication, document, etc.)› Development Team in Scrum is self-organizing.13
    •  Scrum Master› Accountable for removing difficulties for theability of the team to deliver the sprintgoal/deliverables.› Scrum Master is not the team leader.› Scrum Master ensures that the Scrum processis used as intended.› It is recommended that this role not becombined with that of Scrum Master.14
    •  Stakeholders› Are the customers, vendors.› They are only directly involved in the processduring the sprint reviews. Managers› People who control the environment.15
    • 16
    •  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 portionsof a product. The Sprint backlog come from the product backlog. Development is timeboxed such that the sprint mustend on time. If requirements are not completed forany reason they are left out and returned to theproduct backlog.17
    •  If requirements are not completed forany reason they are left out andreturned to the product backlog. If requirements are not completed forany reason they are left out andreturned to the product backlog. A key principle of Scrum is its recognitionthat during a project the customers canchange their minds about what theywant and need.18
    •  Daily Scrum› Guidelines: All members of the development Team comeprepared with the updates for the meeting. The meeting starts precisely on time even if somedevelopment team members are missing. The meeting should happen at the same locationand same time every day. The meeting length is set (timeboxed) to 15minutes. All are welcome, but normally only the core rolesspeak.19
    • › Main points: What have you done since yesterday? What are you planning to do today? Any impediments/stumbling blocks?20
    •  Backlog grooming: storytime› This is the process of estimating the existingbacklog using effort/points› Refining the acceptance criteria for individualstories› Breaking larger stories into smaller stories.› Guidelines: Meetings should not be longer than an hour Meeting does not include breaking stories intotasks The team can decide how many meetings areneeded per week.21
    •  Scrum of Scrums› Working With Multiple Scrum Teams› Each day normally after the Daily Scrum.› Guidelines: Allow clusters of teams to discuss theirwork, focusing especially on areas of overlapand integration. A designated person from each team attends.22
    • › Main Points: What has your team done since we last met? What will your team do before we meetagain? Is anything slowing your team down or gettingin their way? Are you about to put something in anotherteam’s way?23
    •  Sprint planning meeting› At the beginning of the sprint cycle.› Guidelines: Eight-hour time limit (1st four hours) Entire team: dialog for prioritizing theProduct Backlog. (2nd four hours) Development Team: hashing out aplan for the Sprint, resulting in the Sprint Backlog.24
    • › Main Points: Select what work is to be done. Prepare the Sprint Backlog that details thetime it will take to do that work, with the entireteam. Identify and communicate how much of thework is likely to be done during the currentsprint.25
    •  Sprint review meeting› At the end of a sprint cycle.› Guidelines: Four-hour time limit.› Main Points: Review the work that was completed and notcompleted. Present the completed work to thestakeholders. Incomplete work cannot be demonstrated26
    •  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
    •  Product Backlog› Is an ordered list of "requirements" that ismaintained for a product.› It contains Product Backlog Items that areordered by the Product Owner.› The features added to the backlog arecommonly written in story format.› The product backlog contains rough estimatesof both business value and development effort.› Business values are the responsibility of theProduct Owner and estimated efforts aredetermined by the Development Team.28
    •  Sprint Backlog› Is the list of work the Development Team mustaddress during the next sprint.› Is derived by selecting stories/features from the topof the product backlog until the Development Teamfeels it has enough work to fill the sprint.› Development Team should keep in mind the velocityof its previous Sprints.› The stories/features are broken down into tasks bythe Development Team.› Development Team understands exactly what todo, and potentially, anyone can pick a task from thelist.29
    •  Sprint Backlog30
    •  Increment› Is the sum of all the Product Backlog Itemscompleted during a sprint and all previoussprints. Burn down› Is a publicly displayed chart showing remainingwork 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
    •  Burn down32
    • 33
    •  http://en.wikipedia.org/wiki/Agile_software_development Agile For Dummies, CA Technologies Edition The Art of Agile Development34