The way we work is highly dependent on task and the client’s needs, but we can provide a general, most commonly used, simplified schema (for example, when creating a new application):
- A series of meetings with the client that allows us to understand the specificity of his business issues and expectations
- Present our initial solution proposal
- Develop introductory solution concept and requirements which suit to both interested parties.
- Perform a comprehensive business analysis and prepare a customer requirement specification document
- Preparation of the action plan
- Client acceptance
- Start the right developing process
The competent manufacturing process is often conducted in SCRUM methodology. Very general assumptions are that in the project we have constant:
Time and quality are invariable – time is predetermined (eg year) and quality is high. We control the range of functionality we can perform at a specific time. If the range of functionality increases, also increases the time. At a fixed and predetermined time, which usually ranges from 2 weeks to a month plan tasks for the next period called Sprint. After each sprint, the team is showing progress to the customer, who can respond to changes and keep them in the right direction. After the presentation, tasks are set for the next Sprint and the whole process is repeated.
This is obviously a very brief description, if someone is interested in expanding their knowledge about Scrum, I recommend reading professional literature.