Develop Initial Product/Project Management and Architecture Practices

[fjbo-net]

Research and implement approaches and methodologies for managing projects/products based on the following:

• Enable active team collaboration with clear objectives and direction, but also allow room for developers to try and propose new features.
• Allow multiple developers to work in multiple projects, or a single project at a time without interfering in each other's work and let the projects to take as many changes as they are produced.
• Have an obvious and intuitive development and release methodology and organization that is easy to understand and as familiar as possible to newcomers.
• Have efficient versioning that is clear for development, maintenance and distribution.
• Keep in mind good and universal coding and documenting practices to overwhelm newcomers or developers as least as possible.
• Projects must not overlap with each other; however, they should be able to build on top of each other when implementing common logic.
• Projects/products must be modular.
• Projects/products must be testable.
• Projects must support multiple environments, at least the following:
  • Local: this is the environment of developers' machines.
  • Development: this is a shared environment to publish work in progress.
  • QA/Testing: this is a shared pre-release environment which should emulate production environment and behavior.
  • Production: this is the environment that is exposed to end-users.
• Development environments should be setup seamlessly at any level to reduce environment changes and reconfiguration as much as possible.
  • Dependencies should be easy to understand, install, maintain and update.
  • Versions of modules and submodules should be manage by the build process/toolkits and must not be maintained separately by developers to get the project to build or run.
• Development and Run-time environments must be reproducible and controllable.
• Products must be scalable for:
  • Development: Development tasks should be able to be completed by a single developer or several developers.
  • Distribution: Publishing a product should be able to be distributed to a single user or multiple users.
• Most projects will be developed in multiple programming languages (or target environments).

[fjbo-net]

Created new issue #2 to cover how to make objectives clear in order to drive the development efforts towards them.

[fjbo-net]

This issue's progress will be tracked by the The Cotheca Docs, Pre-Alpha milestone

[fjbo-net]

Created new issue (#3) to define the initial procedures or strategies for allowing the best collaborative workflow as possible.

[fjbo-net]

Created new issue (#4) to define the initial methodologies to be used for product releases.

[fjbo-net]

Created new issue (#5) to establish versioning conventions.

[fjbo-net]

Created new issue (#6) to define initial practices for documentation (for both, end-users, and contributors).

[fjbo-net]

Created new issue (#7) to establish an initial version of a style guide for the most fundamental guidelines for separation of concerns.

[fjbo-net]

Created new issue (#8) to define initial practices and conventions for Quality Assurance and Testing.

[fjbo-net]

Created new issue (#9) to cover researching and defining initial practices for deployment strategies.

[fjbo-net]

Updated the size and priority of this issue for Sprint 2023/3.1 as it was a bit conflicting with #2.

[fjbo-net]

Rolling over to Sprint 2

[fjbo-net]

Rolling over to Sprint 3.

[fjbo-net]

Rolling over to Sprint 4