maexware solutions GmbH

We first establish:

• Through a kick-off/pitch/interview (usually NDA already exchanged by then)
  • Who is the company and what does it do? 
  • What industry is the company in and which industries does it serve (or which clientele)
  • What are the requirements and the project goal?
  • What and how should the project goal serve
  • What budget is available
  • Necessary compromises and project boundaries to establish the robustness of the realization. 

Estimation, project structure, offer:

• Definition of requirements and estimation
• Definition of milestones (and epics, if sub-projects are formed)
• Determination of potential team/resource planning and determination of revenue period
• Creation of offer/BV/SLA contract - budgeting

On acceptance or after iterations:

• Create project in project tool chain 
  • Board
  • SEP/RP
  • Milestones
  • Tickets
  • Deadlines
• Resource planning commit and team deadlines internally
• Start of defined processing
• Iteration and consultation with the client either in the project tool chain, in the development system, on a report basis or at fixed intervals.

On fulfillment of requirements:

• Acceptance with customer, both atomically possible per requirement or per milestone.
• Possible iterations or requirement changes, if necessary with atomic re-estimation and budget change

Endpoint: If all milestones or requirements are quantitatively and qualitatively fulfilled, the project is completed. requirements are quantitatively and qualitatively fulfilled, the entire project is completed - the status "completed" for individual milestones or requirements is independent of the status "completed" of the overall project.

We take into account the company, the industry, the willingness to invest and the desired "outcome". In doing so, we clearly define requirements that fit the resulting profile and also clearly clarify possible effects of desired requirements that may not fit the existing profile. A project is then either budgeted as a fixed-price offer or as part of a support agreement/SLA.

Statistically, our customer is most often as follows:

• Embedded in a medium-sized company or national industry. 
• He has designated positions and responsible persons for the areas of the company involved, in line with his project request. 
• Often, but not always, the customer has a technical contact who can grasp the many facets of digitalization and its technological possibilities and make well-founded decisions.
• Often, but not always, the customer has a sales or marketing manager who can grasp the many facets of digitalization and its sales possibilities and make well-founded decisions.