Quick Reads (Under 5 Minutes)

#ReasonsWhyAgileFails: 5) Quitting during the early, conflict ridden stages before realizing any benefits because, “It’s not working

Using Jeff Patton story mapping book as external conscience to spend time with users, prototype in multiple rounds, remain open to change.

Setting up node and angular on suggestion it may be our way to build rich web apps within windows infrastructure.

As a software developer, walking through a paper prototype with a prospective power user is exhilarating.

What brings me joy in my work? Mutual loyalty, comraderie, human scale and something interesting to make.

Product owner is like acting in a bio pic. I want to empathize enough with the user community that I can play them in the movie.

By the way, “It needs to do everything I envision for it to be useful.” is a great description of a useless feature.

I have no confidence that I can predict end user behavior. I am gaining more confidence that I can learn from and react to it.

Use cases, personas, paper prototypes - tools for learning about users so I can better represent them when I collaborate with fellow devs.

I am treating requirements gathering as iterative application development with different tools.

Is the distinction between a problem and an opportunity not the value at stake but what compels you to address it?

I’m conducting user interviews. Different ways of working to different outputs. Some use existing systems. most use Word.