![]() ![]() What do you know and what do you need to find out? ![]() Validate assumptions – Identify knowledge gaps and risks. Get clear on objectives and possible solutions. Problem space – Explain why solving this problem matters to customers and to the business. The poster is split into 3 parts to support this evolution: Then share it with your project sponsors as early as possible to get their feedback, which you'll incorporate in future sessions as your project develops. In the first session, focus on defining the problem space. Project posters get filled out over the course of several sessions with your team, so don't worry about doing it all in one go. The project's core participants: full-time owner, project manager, product manager, developer, designer, analyst, etc. Include the minimum amount of information you need to communicate what you're doing, why you're doing it, how you'll measure success, and your go/no-go decision.Īlready waist-deep in execution mode? No worries. Project posters can (and should!) be created once a project is already underway so your team stays focused on solving the main problems. But it's not a detailed requirements doc. A project poster might be just the cure for what ails you.Īs soon as you've started thinking about a new project, run this play to capture and communicate your ideas. ![]() Stakeholders are leaving comments and questions on all of them, which distracts your team from their core work. Research and ideas get scattered across a zillion different Confluence pages. It's hard enough getting everyone on your team to agree on what problem you're trying to solve and how you'll solve it – let alone keeping the people around you in the loop. Let's face it: medium- and large-sized projects can be squirrelly. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |