Agile For Teams

Agile For Teams

Matt Kocaj
Buy on Leanpub

Table of Contents

Agile For Teams

  • Vision
  • What is this #agileforteams thing about?
  • Why should you care about Agile?
    • Because you care about delivery
    • Because you care about your team’s morale
    • You care about cost, optimisation and efficiency
    • You care about building the right thing more than the wrong thing really productively
    • You care because using the #agileforteams process, you stand to gain:
    • Questions and Actions
  • What is Agile?
    • Agile is open ended, so you need guidance
    • The answer is always: It depends.
    • Process first, Tooling second
    • Questions and Actions
  • Part 1: The Retrospective
    • Questions and Actions
  • Part 2: The Agile “iterative” cycles
    • Loops, feedback and getting up to speed
    • So what are these “loops” then?
  • The Principle of #smallbatches
    • Because Small is Fast
    • Because Small is Easier
    • Because Smaller is Clearer
    • Because Small == Low Risk
    • Because Small gives you Fast Feedback
    • Small often removes dependencies
    • So how do you get to Small?
  • Pivotal Tracker
    • Compared to other tools
    • The Killer Feature
    • Questions and Actions
  • Part 3: The Story Lifecycle
    • Writing a high-quality Story
    • Defining a high-quality Story
    • Estimating a Story
    • Starting
    • Building
    • Mainline Development
    • Automated Testing
    • Continuous Monitoring in Production
    • Fast Deployments
    • Simple Architecture
    • So what do you get in return?
    • Finishing
    • Delivering
    • Acceptance (sign off) and Rejections
    • Rinse and Repeat
    • Questions and Actions
  • Part 4: Points on the Scoreboard
    • When is it going to happen?
    • Why is Velocity so important?
    • An Agile process needs to be sustainable
  • Thoughts on Bugs and Chores
    • Bugs
    • Chores
  • Part 5: How can I get this happening in my team today?
    • Do your stakeholders need convincing?
    • What new part of your project is Low Risk?
    • Just bite the bullet and do a Hard Cutover.
  • Final thoughts, housekeeping and parting inspiration
Agile For Teams/overview

Agile For Teams

course_overview

#agileforteams is a cookbook for pragmatic software development, scientific work tracking and estimation, evidence based decision making, and practical advice

count_chapters
begin_reading
download
p_implied_book_part_name

Agile For Teams13 chapters

Begin ›
  1. Vision

  2. What is this #agileforteams thing about?

  3. Why should you care about Agile?

  4. What is Agile?

  5. Part 1: The Retrospective

  6. Part 2: The Agile “iterative” cycles

  7. The Principle of #smallbatches

  8. Pivotal Tracker

  9. Part 3: The Story Lifecycle

  10. Part 4: Points on the Scoreboard

  11. Thoughts on Bugs and Chores

  12. Part 5: How can I get this happening in my team today?

  13. Final thoughts, housekeeping and parting inspiration