Tag Archives: agile


Scrum development


A key principle of Scrum is its recognition that during a project the customers can change their minds about what they want and need (often called “requirements churn”), and that unpredicted challenges cannot be easily addressed in a traditional predictive or planned manner. As such, Scrum adopts an empirical approach—accepting that the problem cannot be fully understood or defined, focusing instead on maximizing the team’s ability to deliver quickly and respond to emerging requirements.

Delivery every iteration something usable “releasable” to customer.

Continue reading


Creating Effective User Stories


User story

  • placeholder for conversation
  • Independent
  • Negotiable
  • Valuable – for end user
  • Estimate-able
  • Small
  • Testable


  • Brief – designed to
  • High level – defer details

Are not:

  • Detailed – defers design to last responsible moment
  • Set in stone – designed to be flexible

The story format

As a {role} I want to {achievement} So that {confirmation}

  • {role} == group of people
  • {achievement} == what we want to achieve
  • {confirmation} == result of action, acceptance criteria

Continue reading