- Created by Andreas Rosenqvist, last modified by Joel Amundberg on Mar 26, 2020
Event:
Review Criteria Meeting
Date & Time:
26 March 2020 TBA
Place:
From home.
Attendants:
Summary:
Notes:
Review Criteria
In order to pass the R1 review the project and the team should be in control over the following areas:
- Agreed commitment with the customer.
- Defined roles and process.
- Established progress.
- Risks identified and handling.
- Prioritized requirements.
- Requirements on User Story level.
- Show ability to determine when the requirement is completed.
- Estimations and overall plan for the reminder of the project
- Sprint planning connected to the requirements.
- Time reporting procedures.
- Budget used, and predictions.
- Control over required resources.
- Technical dependencies.
- Approach for testing.
- Documentation supporting traceability.
Answers:
- Agreed commitment with the customer:
- The commitment has been completed, and can be found here: Commitment
- The Customer is taking a hands-off approach, and has left the decision making power to the team.
- Defined roles and process:
- Yes, we have established roles:
- Nizaris taking up the role of Project Owner/Team Leader
- Andreas Rosenqvistis taking up the role of Scrum Master
- Joel Amundbergis taking up the role of Test Lead
- Both Wissam Sawahand Rickard Hellmanis taking up roles as Developers
- Yes, we have standardized processes:
- Daily Scrums
- Sprint Planning meetings
- Sprint Review meetings
- Sprint Retrospective meetings
- Yes, we have established roles:
- Established progress:
- Yes, we are establishing our progress at a traceable rate:
- Scrum board keeping track of our backlogs, our current active tasks, and the done tasks.
- Burndown chart reading from our Scrum board for progress tracking.
- Yes, we are establishing our progress at a traceable rate:
- Risks identified and handling:
- We have certain risks handled, for example:
- We are staying quarantined at home to reduce the risks of getting sick.
- We have weekly meetings to determine our progress and decide if we need to adjust our commitment to be able to deliver what we promised.
- We are following Agile principles and are adjusting after the circumstances that we find ourselves in.
- We have certain risks handled, for example:
- Prioritized requirements:
- Yes, we have our requirements and user stories prioritized on our scrum board.
- Requirements on User Story level:
- Yes, we have all our backlog items written up as user stories.
- Estimations and overall plan for the reminder of the project:
- We use our burndown chart to track our progress and estimate how much we have left to do.
- We also use our Sprint Planning and Sprint Review meetings to keep on top of our current velocity
- Time reporting procedures:
- We use our Project Diaries to report individual progress and time tracking.
- We will attempt to keep our scheduled budget, but would not be too surprised if we go over budget if needed to deliver a better product.
- Control over required resources:
- Yes, we have full control over the required resources due to:
- We have servers provided by the customer for deploying our plugin and testing it in a live environment.
- We have access to the necessary programming tools and libraries due to them being open source.
- We have access to the OpenStack community to aid us in situations where we have questions.
- Yes, we have full control over the required resources due to:
- Technical dependencies:
- Python, Django, AngularJS, HTML, CSS, OpenStack, a Linux distro for running everything.
- Approach for testing:
- Currently manual testing of features, but we are starting a course in Basic System Verification which will hopefully give us better ideas how to work.
- Documentation supporting traceability:
- We have created a very well documented wiki where we have our meeting protocols, research data and much more.
- No labels
1 Comment
Anonymous
desde esta descarga.