Once we have gained a clear understanding of your requirements, we start the implementation phase(s) according to an Agile- and GitFlow based approach using Micro Statement of Works or a Large Statement of Work, whatever is applicable:
- We utilize a remote, semi-agile approach with a weekly meeting with a Product Owner or Business Analyst or Project Manager
- We will have agreed to a daily timeframe window in which we are able to consult with your domain experts for when questions arise; this is capped
- Test plans will be delivered by the Customer when using a Subscription; exception is that we do this but this will incur an additional fee, but it is not our preferred modi operandi and is thus an exception
- Testing by factually will be performed and accepted or rejected by the Customer, with consideration given to agreed to functionality
- After functionally and technically considered correct, an upload to GitHub will be performed where applicable
Caveats
- Just to be clear, factually does not release the artefacts to test- or production environments, that is a Customer responsibility. An exception could be Databricks on AZURE where we can target the appropriate Workspace
- Whilst flexibility and adaptability throughout a project, scrum phase allows for adjustments based on feedback and changing needs and is ideal, this fits obviously less with a Subscription-based approach with a fixed price. That has been either factored in at the agreement to a formal statement of work, or is extra cost for a Subscription
- In some special cases a visit on-site may be perfomed, but this is an exception which incurs travel costs and such
- In terms of Cloud and Hyperscaler, we focus primarily on AZURE