Agile Best Practices - gits5213/InterviewProject GitHub Wiki

Welcome to Agile Best Practices!!

Lean - Agile For Teams Training

SDM Transformation Vision

  1. People
  2. Process
  3. Technology
  4. Productivity
  5. Environment

**Leadership Objectives **

  1. Gols
  2. Values
  3. Outcomes Introduction
  4. Name & Roles
  5. Time with company
  6. How much experience you have with Agile?

Overview During the next two ays, we will cover these topics

Day One

Introduction 1. Familiarity with Agile 1. Team working agreement 1. A journey of Learning

  • Why Lean - Agile Adoption?
  • Lean - Agile Frameworks
    • XP
    • Kanban & Lean Flow
    • Srum
  • Agile Teams
  • Scrum Roles
  • Backlog Artifacts
  • Product Backlog

Day Two

  • Story Estimation & Planning locker
  • Scrum Ceremonies
  • Metrics

Agile at scale

 * We thought we'd be developing like this
 * But sometimes it feels like this
 * And our retrospectives read like this
 * Why Do Our Retrospectives Products These Outcomes?
 * Design a System Organized for the Flow Of Value
 * Many Features are Never Used by a Majority of Users

Six Reasons Why Organization Use Agile

    1. Faster Time to Market
    1. Ability to Manage Change Priority
    1. Alignment with Business and with IT
    1. Enhance Software Quality
    1. Early Return on Investment
    1. Early Risk Reduction 

 * Industry Survey of Actual Improvements from implementing Agile 
 * Establish a Sense of Urgency
 * Where is the threat coming from?
 * Further Complicating these challenges is a rapidly evolving competitive landscape
 * We have seen real business benefits in the areas where we have already adopted the Lean/Agile Methodology
 * Agile vs Waterfall 

Agile Value Proposition

    1. Visibility
    1. Adaptability
    1. Value
    1. Risk
 * Delivery Paradigm Shift

Introduction to Lean - Agile

  • Agile is a Culture
  • What is Lean?
  • The Agile Manifesto
  • Agile Manifesto - Snowbird Ski Resort Utah

Agile Manifesto Values - What do they mean?

  1. Individuals and interactions over Process and tools
  2. Working software over Comprehensive documentation
  3. Customer Collaboration over Contract negotiations
  4. Responding to Change over Following a plan
  • Agile Principle

Lean-Agile Frameworks: Extreme Programming (XP)

Extreme Programming Methodology 1. Definition 1. Use cases

Lean-Agile Frameworks: Kanban & Lean Flow

The Kanban Methodology 1. Definition 1. Use cases

  • Kanban Principale
  • Kanban

Lean-Agile Frameworks: Scrum

The Scrum Methodology 1. Definition 1. Use cases

  • Terminology
  • The Scrum Framework
  • Scrum in 100 words
  • Scrum-3 Pillars
    1. Transparency
    2. Inspection
    3. Adaption

5 Scrum Values

  1. Commitment
  1. Focus
  1. Openness
  1. Respect
  1. Courage

The Lean-Agility Space

The Agile Team

 1. Some Truths about the Teams
 1. Stages of Team Development
 1. The five dysfunction of a team 
 1. How Scrum Helps the Five Dysfunctions
 1. Your role on Lean-Agile Teams
 1. Lean-Agile Team benefits
 1. Team happiness
 1. Continuous Improvement

Scrum Roles

 1. The Scrum Framework 
 1. Product Owner
 1. The Product Owner Attributes

The Scrum Framework - Scrum Master

 1. Scrum Master
 1. The Scrum Master Additional Responsibilities
 1. Demonstrating servant leadership

The Scrum Framework - Development Team

 1. Development Team 
 1. The Development team
 1. Development Team Attributes
 1. Cross Function Teams
 1. Cross Function People 
 1. Team Discussion Responsibilities

BackLog Artifacts