Analysis & Offer

Owner: BA Last revision: 12.11.2021

Even before an offer goes out to a client or a contract is signed, a lot of steps have to be taken to ensure the budgets and deadlines are realistic, and product quality can be assured.

• Sending Quotations

Sending Quotations#

• Creating quotation should be done using our estimate template ↗
• Estimates - whenever possible - should be done by at least two team members using planning poker.
• Estimates should be made for the following activities:
  • Specification
  • Wireframing
  • Design
  • Sitebuild
  • Development (broken down into subtasks of no more than 8 hours)
  • Automated testing
  • Code reviews
  • Data migration
  • DevOps
  • Documentation (do they require up-to-date class diagrams / data models / api docs?)
  • Manual testing
  • PM
• Estimated hours for each development subtask should fit in slots of 1, 2, 4, 8 hours
• Estimate should be transformed into quotations, using our quotations template [HU] ↗ or ↗ (@TODO) [EN] ↗ or ↗ (@TODO)

When estimating, take into consideration what the team will look like, what their competencies are and if they require extra time to learn a new tech stack.

Resources#

• Estimates template ↗
• Quotations template [HU] ↗ or ↗ (@TODO) [EN] ↗ or ↗ (@TODO)

Greenfield Projects#

• Create specification (user stories organised into backlog with MoSCoW method)
• Create wireframes (where necessary)
• Create high definition prototypes (where necessary)

Project Takeovers#

• Do we have a takeover documentation? If not, create it!