Posts Tagged ‘agile’

User stories

August 28, 2017

“The real goal of user stories is shared understanding.”

Jeff Patton – User story mapping, p. xxxiv

Advertisements

Build less

August 28, 2017

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

User story

October 21, 2014

Title (one line describing the story)

Narrative:
As a [role]
I want [feature]
So that [benefit]

Acceptance Criteria: (presented as Scenarios)

Scenario 1: Title
Given [context]
And [some more context]…
When [event]
Then [outcome]
And [another outcome]…

Scenario 2: …

Project Management Triangle and Agile

April 17, 2013

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

July 24, 2012

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?

Agile priorities

April 19, 2010

Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan

“That is, while there is value in the items on the right, we value the items on the left more.”—The Manifesto for Agile Software Development

From: Peter Hornsby Can UX be agile?

UX and Agile

March 15, 2010

“(UX design work) also needs to lend itself to a dedicated chunk of time purely to refactor the function of a solution to accommodate the consistency and goals of form.”

Scott Barnes: Can you mix UX with Agile?

Agile and UCD: Agile is good for refining, not defining.

February 1, 2010

“Agile is good for refining, not defining.

(…) if you know what your requirements are and these have been properly informed with user research, comparative analysis, business objectives, and analysis of what content you have and what you can technically achieve, then Agile alone can work well.”

Anthony Colfelt: Bringing User Centered Design to the Agile Environment

User Interface Flow Models

January 5, 2010

Another common diagram to create is a user interface (UI) navigation or UI-flow diagram (…) to explore how you will architect the UI of your system by exploring the flow between major UI elements, including both screens/pages and reports. This is critical to your system’s success because the user interface is the system to your stakeholders. Not the technology. Not the data. Not really cool frameworks that you’re working with. If you do not architect the user interface effectively you run the risk that you will build a system that your stakeholders aren’t interested in working with. See example from the book ‘Maturing usability

Scott W Ambler

Agile: 3 thoughts

January 5, 2010
  1. Don’t agree on a fixed price for agile pojects.
  2. The client needs to understand and agree to employ agile methods. Introducing Agile through the back door will cause lots of trouble (“We said right from the start: we wanted this (…) feature”) and extra cost.
  3. The whole production team will need to think and work agile.