Scott Sehlhorst has been providing product management and strategy consulting services through Tyner Blain since 2005. Prior to that, he worked for an enterprise software vendor for eight years and as an electromechanical design engineer for another eight years. Scott's BS in mechanical engineering is from Carnegie Mellon University. Scott believes passionately that it isn't enough to build your product right; you also have to build the right product. Follow Scott on Twitter at http://twitter.com/#!/sehlhorst.
Do you have a question for our experts?
Contributions from Scott Sehlhorst
- Software product success: Maintain customer focus
- Product failure: Software too complicated to use
- Predictive root cause analysis prevents product failure
- Cater to the buyer persona as well as the end-user
- Software requirement specifications for mobile apps
- Software requirements specification: Don't be vague
- User experience design requirements for mobile apps
- Get execs to take part in writing business requirements
- Social media surveys: A tool for better requirements?
- Requirements definition: Get developers involved early
- Setting priorities: A software project team exercise
- Protecting software: Writing security requirements
- Do business stakeholders lose requirements in Agile?
- Gathering project requirements up front in Agile
- Managing requirements with multiple stakeholders
- Scaling Agile requirements management to the enterprise
- Using a burn down chart to measure project progress
- How project sponsors can successfully manage changes
- Optimizing requirements management in Agile, Waterfall
- How product managers best manage requirements