TL; DR: Create Personas with the Help of the Engineers
Creating valuable software requires knowing the customer—we all agree on that, right? The first question that then comes to mind is how to support this product discovery process in a meaningful manner in an agile environment? And the second question follows swiftly: who shall participate in the process—designers and business analysts or the engineers, too?
Read on and learn why personas are useful for product discovery purposes, how to create personas, and why the complete team—including the engineers—needs to participate in their creation.
This fourth part of the Lean User Tests series focuses on equipment and location: What hard- and software do you need to run your user tests, and where to run them? (Spoiler alert: It’s preferably not your office.)
How are your preparations progressing? If anything is impeding you from reaching this goal, please do not hesitate to contact me by commenting this post, and I will gladly help you.
Stakeholder communication: It is simply not enough for an agile product development organization to create great code and ship the resulting product like a clockwork. You also need to talk about it, particularly in the beginning of your agile transition. Marketing the agile journey of product and engineering to the rest of the organization—and thus getting their buy-in—is a critical success factor to step up the game: You want to become agile, not “do agile”.
So, learn more about ten proven stakeholder communications tactics that contribute to making this happen.
This part of the Lean User Tests series focuses on selecting and inviting interviewees: Who is a suitable candidate, how to invite them and why you will need replacement candidates.
You should now be around three to four weeks away from your next—or first—user test. If anything is impeding you from reaching that goal, please do not hesitate to contact me by commenting this post, and I will gladly help you.