daveshap
Define Project Methodology
Discussion in #15
User Story
As a project manager in an OSS project, I want to choose a methodology that best fits the needs of my team and project, so that we can successfully deliver high-quality software efficiently.
I want to consider factors such as team size, geographic distribution, project complexity, and stakeholders' requirements when evaluating different methodologies. I want to be able to weigh the pros and cons of each methodology and make an informed decision.
I want to be able to easily communicate the selected methodology to my team and stakeholders, and ensure that everyone is aligned on the process we will use to deliver the project. Additionally, I want the chosen methodology to be flexible enough to adapt to changes in the project as needed.
By selecting the right methodology for our OSS project, I want to set my team up for success and ensure that we can deliver high-quality software that meets the needs of our stakeholders.
Acceptance Criteria
1. Aligns with RAVEN project goals and objectives: The methodology must support the overall goals and objectives of the RAVEN project and allow for flexibility in adapting to changing requirements.
2. Supports GitHub as a project management tool: The methodology must be compatible with the use of GitHub as the primary project management tool and allow for efficient tracking and reporting of progress.
3. Incorporates Agile principles: The methodology must embody Agile principles such as iteration, continuous improvement, collaboration, and customer focus.
4. Supports cross-functional collaboration: The methodology must promote collaboration between feature teams, stakeholders, and other project participants and encourage cross-functional collaboration.
5. Promotes continuous delivery: The methodology should enable continuous delivery of value to customers and facilitate the delivery of new features and functionalities.
6. Fosters transparency and accountability: The methodology must provide transparency in decision-making and accountability for project outcomes, and ensure that all participants are aware of their roles and responsibilities.
7. Encourages experimentation and learning: The methodology must support a culture of experimentation, learning, and continuous improvement, and promote a continuous learning environment for teams.
