Cobuild Lab's documentation for Project Management and Software Development Conventions

This is the main repositoty of documentation for the company. In here we set up all the agreements for the different processes of the Organization.

1. Project Management:

Process to follow for the Process of Project Management in Cobuild Lab.

2. Terms Definition Link

3. Roles and Responsabilities Link

4. PRE project Activities

Here we outline the main activities when starting a project in a non-necessary sequential order:

1. CREATE THE PROJECT SLACK CHANNEL:

When a project is started the first step is to assemble the team in a slack dedicated project channel. Project Channel names start with a double hyphen “--”, followe by the short name of the project in lowercase. Example: “--awaken-flow”, “--c2g”

2. CREATE THE PROJECT FOLDER:

The Project folder must be created under the main “Projects” folder managed by the organization. (Google Drive)

3. SET UP GITHUB:

• Create the code repositories under the (repositories naming convention)[/conventions/repository-name.md]
• Set up the Kanban project with the Kanban Project Conventions (TODO)

7. 3. PROVISIONING:

Infrastructure Provisioning: Servers, 8base workspace, hosting, GitHub, slack channel, buddy works, DNS setup, etc

6. Set Github Kanban with columns and labels
7. Subscribe Github notifications to Slack Channel
8. The full scope of the project must be shared with the Development Team to create an Execution Plan with milestones and deliverables.
9. Create Milestones in Github Project Kanban
10. Provide access to the team members to the Github repositiories, Project Folder and any other external assets (Invision, XD, Auth0, AWS, Buddy works, etc)
11. Set Fisherman (activity Tracking for developers) for the project’s repositories tracking and standups.
12. Complete all User Stories (Issues or Tickets) in the project scope on a Planning meeting.
13. Set the meetings for the Planning and Daily Standups with the development team.
14. Set the communication channels with the Customer.
15. Kickoff meeting with the Development Team.
16. Ensure that all requirements for the full development of the project are in place or scheduled to be in place.
17. High level Data model

5. IN project Activities (Software Development Process)

2.1. Issues Quality Test:

Ticket specification is responsabilitye of the Project Manager, QA and Technical Lead.

• If the Issue is estimated to be longer than 2 days, it needs to be split.
• If the Issue doesn't have the specification completed, it needs to be completed.
• If the Issue doesn't have the technical specification completed, it needs to be completed.
• If the Issue requires a UI and it doesn't have it

2.2. Test Case

• Use the Wiki to define Business processes that need to be tested.

  6. POST project Activities (Warranty and Support)

2. Software Development Conventions:

The complete list of conventions and agreements for codebases can be found in here

3. TODO:

1. Requirement Management: (documentacion de requerimientos, alcance del requerimiento, cambio de alcance).
2. Coding Conventions: https://github.com/cobuildlab/conventions
3. Unit Testing, Check lists, Definition of Done
4. Project Management Strategy: https://docs.google.com/document/d/1AGbBEnYg5_k0Bd-e4j-TdmNk3qu4vdAYhExS9kD6C-Q/edit (Scrum + XP + Kanban)
5. Environments: https://docs.google.com/document/d/1AGbBEnYg5_k0Bd-e4j-TdmNk3qu4vdAYhExS9kD6C-Q/edit
6. Release processes: Main -> QA, QA -> Stage, Stage -> Prod: https://docs.google.com/presentation/d/1hIx5LVp6RTd7bKj8ZSllu4aZX2gf_w5frNTMq2DGbG0/edit#slide=id.p
7. Quality Assurence: Testing Plan, Test Cases, Issues and Issues reporting
8. Miscelaneos
9. Test Automation
10. Coonstant Education and Training
11. TMMI
12. Template for User Stories
13. Template for CLIENT FEEDBACK (Issue tracking)
14. Release process por environments
15. Roles and responsabilities for Project Management and coordination: https://docs.google.com/document/d/1AGbBEnYg5_k0Bd-e4j-TdmNk3qu4vdAYhExS9kD6C-Q/edit
16. Name releases (versioning): https://semver.org/
17. Emails content for releases to clients
18. Form to incoming request for features / issues / bugs / enhancements / etc
19. TODO list for Env Release
20. TEMPLATE: Follow up emails
21. Client Feedback Spreadsheet: