Each requirement you write represents a single market need, that you either satisfy or fail to satisfy. A well written requirement is independently deliverable and represents an incremental increase in the value of your software. That is the definition of an atomic requirement. Read on to see why atomic requirements […]
Agile / Business Analysis / Product Management / Requirements / Requirements Models / Software development / User Stories
Posted on:
Sprint Backlog – Don’t Solve Half of the Problem
Every team that transitions to agile faces this problem – some stories are too big to fit in a single sprint. Most of the teams that I have worked with have the wrong instinct – to solve half of the problem for all users. The right approach is to first […]
Agile / Foundation series / Requirements / Requirements Models / Software development / Testing / User Stories
Posted on:
Foundation Series: Inside A Scrum Sprint
People who already use Scrum will only find one new thing in this article – a way to communicate what happens inside a sprint that has proven effective for me. People who are new to Scrum who wonder “how do things work inside a sprint?” will see how things work […]
Agile / Kano Analysis / Product Management / Requirements Models / Software development
Posted on:
The One Idea of Your Product
“For what one idea do you want your product to stand in the mind of your customer?” I heard Roger Cauvin ask that question at the most recent ProductCamp Austin [correction – he said it here – thanks Roger], and the quote has been jumping to the front of my […]
Interaction design / Product Management / Requirements / ROI / Software development / User Stories / UX
Posted on:
Measuring Great Design – Mad Libs Input Form
I came across a really interesting article LukeW.com, showing how making changes to the way an input form on a website increased interaction by 25 to 40%. The changes reflect the value of thinking outside-in, investing in user experience, and performance measurement. Bonus: the idea is cool.
Administrivia / Agile / Business Analysis / Prioritization / Product Management / Project Management / Requirements / Requirements gathering / Requirements Models / ROI / Software development / Use Cases
Posted on:
Most Engaging Articles of 2009
Engagement – that’s what this whole product management blogging thing is about. Check out what Tyner Blain readers found to be the most engaging articles in 2009.
Agile / Business Analysis / Interaction design / Interface Design / Product Management / Requirements / Requirements Models / Software development / Use Cases / User Stories / UX
Posted on:
Design-Free Requirements
Design-Free requirements are important for two reasons, and hard for two other reasons. Design-free requirements are hard because you “know what you want” when you should be documenting “why you want it.” Writing design-free requirements can be hard when you don’t trust your development team to “do the right thing” […]
Agile / Interface Design / Product Management / Software development / UX
Posted on:
Agile Prioritization: Which Widget?
Your company is building out a toolkit to support third-party developers. You’ll need a bunch of different types of widgets – combo-boxes, text entry fields, domain-specific controls, etc. You’ve got a long list of desired controls from your customers. You’re agile. What do you build first?
Business Analysis / Interface Design / Product Management / ROI / Software development / Usability / UX
Posted on:
Modeling User Competency
Perpetually intermediate (competent) users. Users who briefly exist as novice users and never become experts. Most of your users are competent, and you should design for them. Competent users have different needs and different expectations than novice or expert users. How do you know your user’s competency levels, so you […]