Agile Notes - fcrimins/fcrimins.github.io GitHub Wiki

15 signs you’re doing agile wrong (7/5/16)

Agile no longer addresses the fundamental bottleneck (5/24/16)

  • "The first step in building the right thing is to avoid building wrong things along the way."
  • "In essence what is needed is the adoption of a Lean Startup mindset and the creation of a toolbox of techniques for (in)validation." -- i.e. optimal stopping point

What are User Stories? (3/7/16)

  • "User stories are not requirements, they are a concept to communicate requirements."
  • FWC - If Agile is so effective, then why are there so many articles that try to explain it? Does anyone really get it? And even if there is a subset of people who do get it, how can it be effective given that there are so many people who don't.

Does Scrum Work? (1/5/16)

Agile vs Agility : Agile Is Dead (Long Live Agility) (PT008) (12/16/15)

Two decades of Java: A timeline of the notable events (12/11/15)

Sisyphus on Fire: The Coming Agile Dystopia (12/11/15)

  • Not much more than a rant, but a convincing one.

When Gitflow Stops Being Agile (12/10/15)

Agile Negates the Most Important Benefits of Switching to Functional Programming (12/10/15)

Epics, stories, versions, and sprints (11/4/15)

Modern Agile (11/3/15)

Managing Holidays, Time Off, and Meetings with a Distributed Team (10/23/15)

Do we really need user stories for effective Agile development?

Agile Failure Patterns

Agile Is The New Waterfall (10/13/15)

  • All successful processes are unique. You can’t read a book and go through it’s 12 steps to build great software any more than you can read a book, go through it’s 12 steps and come up with the next big thing.
  • Only add processes that reduce significant actual risk. Create process to help reduce a particular risk IF you can answer yes to one of these three questions: 
    1. Did an actual problem occur that was systemic and not just a one off? _Example: Sally and Bob both repeatedly started working on the same feature, and don’t figure it out for 2 days because there’s no way for them to do so._
    2. Is risk of a problem occurring very high? Example: drives crash often enough that if your source isn’t checked into source control for a month, there’s a real risk of significant loss.
    3. Would a problem have catastrophic consequences? Example: if a wing falls off a plane in flight, it’s game over for everyone on board.

Email: If it hurts, do it more often: Frequency Reduces Difficulty (9/28/15)

Email: More Agile

Email: Agile Tools