INVEST (user stories)

  • I-ndependent
  • N-egotiable
  • V-aluable
  • E-stimable
  • S-hort
  • T-imely
Advertisements

Build less

One of the common misconceptions in software development is that we’re trying to get more output faster. … But if you get the game right, you will realize that your job is not to build more – it’s to build less. Minimize output, and maximise outcome and impact.

Jeff Patton, User story mapping, p. xli

Project Management Triangle and Agile

For team members working in an agile software development environment (if you are not already, it is simply a matter of time), the principles of the old Project Management Triangle still apply. How the cost, scope, and schedule are balanced will always determine the quality (i.e. success) of the project, and this needs to be assessed with each project (i.e. the client requirements). Unfortunately, no one is immune to senior management and project managers trying to upset the balance of the PM Triangle by reducing costs, tightening deadlines, and adding features in the specification (most likely to try and make a sale).

UX and Agile: Tying the knot by Michael Lai

UX strategy and agile process

UX strategy can provide the strategic guidance that agile doesn’t attempt to provide. As Liam Friedland, Senior Director, User Experience at Informatica, puts it: “Agile is a process; ergo a set of tactics. Agile is not a strategy. Sun Tzu provides us with a good understanding of the relationship between these two: ‘Strategy without tactics is the slowest route to victory. Tactics without strategy is the noise before defeat.’”

Paul Bryan: Is UX Strategy Fundamentally Incompatible with Agile or Lean UX?