Why do we need specifications?
What do specifications look like?
What needs to be included?
How detailed should the specifications be?
How much time do you have to spend on it?
Who should be involved in the preparation?
How do you properly prioritize items?
What tools are useful?
Many projects will not bother with specifications, mostly for lack of time. With migration projects, though, the legacy system is often regarded as a supposedly ideal replacement for specifications. Often the client understandably has no idea what requirements need to be placed on the developer team and how detailed they should be. This can have serious consequences.
However, a good specification is a prerequisite if a custom application is supposed to look and function exactly as you imagine it, whether you have your own team develop it or outsource it to a service provider.
We conduct a specification workshop with you where we work together to identify the requirements that are important for your project, prioritize them realistically, and document them ready for the development phase. It is only after this workshop that accurate estimates can be made of the complexity of the project, the quantity and qualification of personnel needed to implement it, and the amount of labour and financial investment required  to achieve the desired result.
During the continued agile project process, the specification is continuously reviewed and adjusted or expanded as required. It also serves as the basis for future software documentation.

Duration: 1-5 days (depending on the project)


■ Involve all for the project necessary persons and divisions
■ Determine the scope of features
■ Prepare a rough specification
■ Define priorities
■ Define milestones & deadlines
■ Define responsibilities