It's thrilling to launch a new tech product or service, not just for the tech team members who will create it but also for team members who will use, market, and/or sell it. Getting input from a variety of stakeholders — particularly end users — can definitely lead to a stronger tech product. However, it can also lead to scope creep.
It's all too easy for tech executives and project managers to cross the fine line between gathering and using useful feedback and attempting to incorporate every item from every stakeholder's wish list into a tech project. While it’s important that those who hold unique insight are heard, it's equally crucial to set and uphold clear boundaries to prevent a tech project from veering off course. In this article, thirteen members of the Forbes Technology Council, including our Co-founder and CEO Jay Goldman, explain the strategies they advise for preventing scope creep on a project and share why these methods are effective. Jay's contribution:
There’s a great collaborative workshop—The $100 Game—you can use to prioritize input while avoiding scope creep. Make a list of everything you could do. Give everyone ten “$10 bills” so they can “buy” their priorities. They can drop $100 for one item or spend $10 each on 10. Tally up the piles to find out what’s really important. Pro tip: Use different color “bills” for each job function if you want an extra data dimension.
Read the article here.
