Skip to content

Latest commit

 

History

History
42 lines (28 loc) · 1.41 KB

project_management.md

File metadata and controls

42 lines (28 loc) · 1.41 KB

Project Management

Project Workflow

PMAP001 - Project Phases

  1. Gather feedback on the most needed feature from users
  2. Specify what is needed by the users in details
  3. Specify how it can be done by the technical team
  4. Specify the interface between the user and the implementation details (API)
  5. Mock the interface to allow all parties to work in parallel
  6. Implement the API endpoints, improve it if necessary
  7. Test the API endpoints
  8. Document the feature by re-using the specifications
  9. Deliver the feature, gather feadback from the users and repeat

Conventions

Conventions help your code being consistent.

PMAC001 - Build A Glossary

When a project becomes complex, some concepts or objects may be called differently by different teams.

For example, for a movie streaming company, a movie could be called:

  • A film by the business team
  • The raw data by the technical team
  • The project by the producer
  • The big buddies by the infrastructure team

You may have already live some confusion because of inconsistent naming. This is why a company needs to build a glossary to ensure that everybody use the term movie for these objects. This improves both internal and external communications.

Source Management

PMAS001 - Use Git

You should use a version control tool to store our source code, such as Git.

Next: Productivity