How do you work with professional services, consulting, field engineers, etc. to make your product better? Do you just treat their inputs as yet another channel for feature requests, or do you engage them as an incredibly potent market-sensing capability?
ProdMgmtTalk / Product Management
Posted on:
Market Insights and Collaboration
In this week’s #ProdMgmtTalk, one of the livelier discussion topics was around gaining insights into your market – and what does that mean (to you)? Steven Haines was the speaker for this session who prompted us to think, and pushed us to rethink our views on market insights. What a […]
Agile / Business Analysis / Requirements / Requirements Models / Software development / User Stories
Posted on:
Agile Documentation
Agile values working software over comprehensive documentation – it is 1/4th of the original manifesto. That doesn’t mean don’t document! It means don’t document more than you need to document. Documentation does have value, but the practice of documenting got excessive – that’s why a reaction to the bad stuff […]
Business Analysis / Requirements
Posted on:
Why Requirements Approval Matters and How To Make It Easier
Getting requirements documents approved can be a pain in the butt. Why do we need to do it in the first place? The approval process is more than just reaching concensus or creating a contract. Done correctly, it presents an opportunity to get more inputs from stakeholders.
Process Improvement / Project Management / Requirements / Software requirements specification
Posted on:
Agile Requirements
One of the key points that enables James’ approach is “tight collaboration†between the program manager and the developers. He talks about the miracles that can happen when you have this, as conversations can cause time to miraculously appear in the schedule. And his use of the toaster analogy is spot on.