• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Agile Basics in 60 minutes
 

Agile Basics in 60 minutes

on

  • 210 views

Agile Basics in 60 Minutes is a new eBook that covers the fundamentals of Agile and Scrum. These slides give you an overview of the main topics.

Agile Basics in 60 Minutes is a new eBook that covers the fundamentals of Agile and Scrum. These slides give you an overview of the main topics.

Statistics

Views

Total Views
210
Views on SlideShare
162
Embed Views
48

Actions

Likes
0
Downloads
6
Comments
0

2 Embeds 48

http://myitcareercoach.com 40
https://twitter.com 8

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

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

    Agile Basics in 60 minutes   Agile Basics in 60 minutes Presentation Transcript

    • Why Are Changes Needed? ● Traditional approach slow and inflexible ● Testing at the end ● Change is discourage
    • Agile Manifesto 1. Individuals and interactions over processes and tools 2. Working software over comprehensive documentation 3. Customer collaboration over contract negotiation 4. Responding to change over following a plan
    • Agile Keys ● The key is to make the process lightweight and adaptive to change. ● Agile asks us to have frequent check ins with stakeholders.
    • Scrum ● Scrum was born out of work on eXtreme programming ● The term “scrum” is reference to a rugby team that moves as a unit.
    • The Benefits of Agile ● Agile emphasizes short cycles or iterations of work ● Agile is also lightweight and adaptable when compared to traditional waterfall software development.
    • The Sprint 1. The Agile process breaks down work into something called a Sprint. 2. The Sprint length can be as short as two weeks or as long as four weeks.
    • The Sprint Backlog ● The stories the team has agreed to work on during the Sprint is called the Sprint backlog. ● These user stories are selected from the product backlog
    • Daily Scrum or Standup One of the most helpful practices in Scrum is the Daily Standup Meeting or Daily Scrum. 1. What did you do yesterday? 2. What will you do today? 3. Is there anything in your way?
    • Scrum Roles 1. The Product Owner brings the business requirements to the team. 2. The Scrum Master is the team coach and leads the team through the Sprint. 3. The Team estimates their stories and makes their own designs and implements them.
    • User Stories User stories are short, simple descriptions of a feature told from the perspective of the person who desires the new functionality, usually a user or customer of the system. —Mike Cohn, Mountain Goat Software
    • Acceptance Criteria Acceptance criteria defines the boundaries of a user story and tell when a story is done.
    • Sprint Retro 1. Examine the successes and failures of the Sprint 2. Try to get the whole teams input 3. Last meeting of the Sprint
    • Product Backlog ● Product backlog is a list of features and changes to be done. ● The product backlog list must be ordered in the priority they should be completed.
    • Backlog Grooming ● The Agile team periodically will meet to groom the backlog. ● Grooming involves reviewing user stories to check for their completeness.
    • Sprint Planning ● Agile team meets to plan next Sprint ● Outcome should be a prioritized list or Sprint Backlog
    • Agile Basics in 60 Minutes Available on Amazon in Kindle format Order now!