Skip to content

Latest commit

 

History

History
36 lines (28 loc) · 2.11 KB

projectLifecycle.md

File metadata and controls

36 lines (28 loc) · 2.11 KB

Project Lifecycle

At Expertizo, all tasks are created as tickets through Trello.

If a ticket is classified as a Project, the following steps take place:

  1. The Task is assigned to a development team or a developer by the Engineering Manager or Project Manager.
  2. Assigned developer(s) creates an estimate (this is a good resource for generating estimations) of the work involved. The creation of this estimate will usually have a deadline assigned by the Engineering Manager or Project Manager, but should usually be done as soon as is pracitcal given other work priorities.
  3. Developer(s) post the estimate to the #general channel using the Geekbot standup following format:

What is your plan till day end?:

Provide estimations for each of the above tasks mentioned.:

  • 3 hrs
  • 2 hrs

Anything blocking your progress?:

  • Forgot password API isn't working anymore.
  1. Follow the Workflow process to complete the Project.

  2. Documentation must be added or updated in the repository for this Project's code.

Planning Document

In order to facilitate proper forethought and planning in a project, a planning document should contain the following, at a minimum:

  • Introduction which identifies the problem/task to be solved, along with relevant context.
  • Presentation of at least three engineering approaches to solve the problem/task.
  • After the presentation of each approach, the pros and cons of each approach should be listed so the approaches can be compared.
  • A summary in which the chosen approach is identified, along with a logical explanation for its selection.
  • Any other relevant information explaining the estimate or project details.

Additional Note

  • Tickets marked with the label Urgent bypass this process and should be worked on immediately.