should it have a product roadmap? • No pain, no gain • Ask forgiveness, not permission • Permissionless innovation • Risk taking – no Product Requirements Document Some characteristics of a Project
should it have a product roadmap? • No pain, no gain • Ask forgiveness, not permission • Permissionless innovation • Risk taking – no Product Requirements Document • Fail fast, fail early – learn, grow and evolve Some characteristics of a Project
your customers • Constrained in that it needs to meet the customer requirements • UX/UI finesse • Scalability is important: how would you help the evolution of the product?
your customers • Constrained in that it needs to meet the customer requirements • UX/UI finesse • Scalability is important: how would you help the evolution of the product? • Branding: project name <> product name
compared with Product people • The motivations of being in a project team is significantly different than being a product team • There may be overlaps, but it is few and far between
can collaborate – sort of a “constitution” • It states the expectations, rules of engagement of all involved in the project • Can a project not have a license? What about Licensing?
can collaborate – sort of a “constitution” • It states the expectations, rules of engagement of all involved in the project • Can a project not have a license? - You could, but not advisable What about Licensing?