Repo for Small Window Assignment
- Preamble
- Project Deadline
- Project Specification
- Useful Links
- Risk Register
- Tenants of Design
- Social Contract
- Other
This is the online repository for the DevOps Project Management Assignment 2021.
The customer would like an on-line system to take in staff details for analysis. SmallWindow is a engineering and tech company. The product that they wish to market is BusIntelligence. The system must take details for new staff and to provide easy to use analysis features. For example, they may wish to have a review all staff which have CompTIA and have DevSecOps training as this may indicate future projects that may be exploited. Keep the analysis simple. The analysis system should be clean and simple. The system needs to take into account the usual details and present simplified graphics. It must be possible to upload files or images. The administrator should be able to access detailed information and edit as appropriate. Once the client enters details it should not be able to be changed by the client.
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.
Ruth G. Lennon
- Damien Gallagher
- Michael Conaghan
- Ronan Clancy
- Sharon Greene
- Sunoj Jose
- John Richard
- Robert Tokarz
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 <specify platform>
Frameworks
Database
Database persistence technology
Define the buisness Requirements
Named queries and database triggers for security
Regex for cleansing and validation of data before sending to the database.
- Project Slack: https://app.slack.com/client/T84LE6L6R/C023LTYQFFY
- GitHub: https://github.com/rlennon/smallwindow21
- Jira: https://studentjira.lyit.ie/projects/SMLWIN21/
For more information visit our other sections
| Section | Description |
|---|---|
| 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
Infrastructure proving to be a real problem, may block being able to release software
Team is finding itself to be running short on time due to other work and study commitments
No PO feedback on software
Unknown technology choices has led to a lot of upskilling required
Changing / ambiguous requirements
Talk of the company being bought out has raised concerns
Lack of rights for toolsets chosen has hindered progress and ability to deliver
<p>Risk Register Template is loaded here.
https://studentjira.lyit.ie/projects/SMLWIN21/issues/SMLWIN21-11?filter=allopenissues
Dedication to clean, secure, performant and self documented code
code Frameworks used
code coverage tool used
Secure code: Regex for cleansing and validation, Named queries and database triggers
performance testing tool to be used
Documentation / code commenting (javadoc)/seperate branch
Datastore for persistence
Testing:
Unit testing
integration testing
UA
Environments:
staging and production
tight configuration management for consistency and reproducibility
automated creation and deployments
integrated and automated pipeline (commit -> test -> deploy)
Github version control:
branches used
version/release management
Agile project management methods/principles (jira)
Stand-ups will occur on Every Wednesday during class and Mondays at 8pm GMT+1 using Automated bot.
The order that people give their updates will be based on alphabetical order 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 Mondays at the end of our sprint on Zoom.
Please add and update items within Jira prior to the sprint planning session.
Sprint retro will at the end of our sprint on Monday at 8pm GMT+1 (timebox retro for 15 minutes, to be organised by the scrum master).
The order that people present their sprint retro updates will be based on alphabetical order of those present at the meeting.
Points raised in the sprint retro will be noted and posted on the slack channel by the Scrum Master. The Scrum Master is rotated per team member every week.
Backlog refinement will happen on the Monday during our sprint.
Task estimation will be done using "planningpoker.com" TBD.
Come prepared to meetings.
Be on time for Stand Ups and meetings.
Mobile phones on silent.
Everyone has equal voice and valuable contribution.
Keep your language and tone professional at all times.
Be honest.
Slack is the preferred method of communication.
Communication in this order: Slack
If a demonstration is required use Zoom, record the session and upload to the Slack channel.
No Slack communications between "<Time and Timezone>" TBD.
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.
Agile way of working.
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.
Sprints will start every Second Monday at 9pm GMT+1.
The Scrum Master role rotates each week, the schedule is available on the on the process section
Jira will be used for task management and planning.
Each member of the team will work 8 per week, unless they are on vacation.
GitworkFlows, Main > develop > feature
The teams team's velocity is calculated by the number of story points we achieve on average in the previous sprints.
The teams current story point velocity is "N/A".
- Story is pointed
- Enough information to start
- Acceptance criteria is defined
- Min of 2 reviewers
- Merged into main
- Deployed successfully
- Deployment Tested
- Reviewed, followed and executed by Reviewer
- Working solution over documentation