BScDevOps Assign - Team
This is the online repository for the DevOps Assignment.
Our product will be delivered using an Agile methodology that embraces the DevOps culture. Please note that our culture embraces change and these documents are treated as living, breathing artefacts that will be continuously updated.
Lewis Barett L00145352 (Permanent)
Refer to BB for deadlines
Clean and simple design
User access levels (client, administrator)
Includes at least one self developed api and one webservice
To be run over
We will be using Django and SQLite IDE will be Pycharm 2023 Community Edition
For more information visit our other sections
Process Describes the companies process Project Log Log of project activities Costings Overview of the project cost Architecture Outlines the architecture Environments Overview of the environment set-up DR Plan Disaster Recovery Plan and procedures Requirements Overview of the requirements for the project SLAs Service level agreements Risk Management How we manage risk Security Overview of security Project Log Team log for the project
These are the current Risks on the project, re-aligned on a weekly basis
The code framework to be used will be Java, we will be programming using the app IntelliJ
SpotBugs: uses static analysis to find bugs in java code.
PMD: Static code anaylsis checking tool. The tool scans Java source files to look for potential vulnerabilities such as coding errors and security flaws. It offers a cheap alternative to the tedious process of continually going over a huge code base. PMD is also capable of detecting other issues, such as dead code and performance issues along with poor code practices and styling. PMD has been installed through GitHub actions to scan code as it is commited.
Unit testing
integration testing
UA
API Testing
staging and production
tight configuration management for consistency and reproducibility
automated creation and deployments
integrated and automated pipeline (commit -> test -> deploy)
branches used
version/release management
Mobile phones be left on silent during sprint sessions and class time.
Be on time for team meetings and class, if you are running late let the group know by sending a message into the Slack channel.
Everyone has an equal voice and valuable contribution.
When you are assigned a job, take ownership of it and keep it up to date, do not be afraid to ask others for help, always be honest about your work.
Do not speak over someone when they are expressing a point, everyone has an equal voice.
No blame culture.
Do not be afraid to ask for help, we are all learning.
No invisble work.
Ask questions to make sure you understand the task given to you.
Try have some fun, team work makes the dream work.
Use Agile methodoligies in the project at all times.
Stand-ups will occur on Every Wednesday/11:30-1:30 during class and Friday on Slack/12:30-1:30
The order that people give their updates will be based starting with the scrum master and going clockwise around the group of those present at the meeting.
Updates will be in the form: What I've done, Impediments, What I plan to do.
Sprint planning will occur at the start of class every week at the end of our sprint.
Please add and update items within <
Slack is the preferred method of communication. we will also be using discord for the generasl quick comunication Communication in this order: Slack, Discord, Microsoft Teams, Outlook If a demonstration is required use Zoom, record the session and upload to the Slack channel. No Slack communications between 9PM and 9AM. Raise a problem as soon as you see it. Respect each other and understand differences in knowledge. All team documents are to be created using Markdown language and shared on GitHub. There are no silly questions, if you don’t understand, ask. Share success stories. Focus on the positives. Don’t make assumptions. Don’t interrupt and cut another person off while they are talking. Listen when someone is talking, don’t interject. Zero tolerance for bullying.
If are assigned a job, take ownership of it and keep it up to date. Stick to your agreed working patterns. Let the team know when you are late or going early. Keep JIRA board updated at all times. Update the Scrum Board as you progress the story i.e. don’t update at standup. Don't be afraid to ask for help. Don't be afraid to give constructive criticism, as long as it is constructive. Solve roadblocks within the team. If the impediment can’t be solved within the team then give it to the Scrum Master. Other Sprints will start after the stand up that happens at the start of class each week. The Scrum Master role rotates each week, the schedule is available on the on the process section Poker Planner will be used for task management and planning. Each member of the team will work approximitely 3 hours per week, unless they are on vacation. Our branching stategy will start with gh then the issue number followed by wip
The teams team's velocity is calculated by the number of story points we achieve on average in the previous sprints. we will be usign the mthodology 1 story point per hour of work
The teams current story point velocity is "16".
Story is pointed Enough information to start Acceptance criteria is defined Definition of Done Code Min of 1 reviewer Merged into main Deployed successfully Deployment Tested Documentation Reviewed, followed and executed by Reviewer Working solution over documentation