Before clients and developers begin building new software together, it is important that both parties have a clear understanding of the end goal.
A requirements workshop lays the foundation for a successful product development that leaves all parties involved with a firm understanding of the project’s objective and how to reach it.
- A “requirements workshop” define the project’s goals (product backlog), as well as the individual steps necessary for their completion (user stories), to be determined in the form of an overall product vision.
- The requirements laid out in the Product Backlog are prioritized, forming a simple, goal-oriented workflow based on the client’s wishes. In this way, the most important aspects of the project are realized in the highest quality, before the implementation of less important features and nice-to-haves.
- As output of a workshop GM will deliver a Software Requirements Specification for the initial months of development or a minimum viable product (MVP).
- The software industry has for decades - and still is - plagued by poor deliveries. Research shows that it’s usually around project requirements it goes wrong. Hence, frequent workshops are good, but paramount to take a new project onboard.
Brown paper bag - exercises, Post-its & a wall, 2-3 days of intense collaborative scope discussions
- Exhaustive Knowledge Transfer session avoiding cost overrun
- They speed up productive time of developers
- Workshops decrease the time spent on non-value adding features
- Fundamentally increases project success rate
- Workshops - contrary to popular belief - do not slow-down ramp-up time or start of development
- Workshops greatly increase accuracy of estimates and deliveries
- Gives quality input for project resolution to all parties involved
The cost of making changes to the scope (project) can be a costly affair if the scope is not clearly defined. Workshops reduces costs that occur later in a software development life-cycle.