Secosol Website

(Replace this with the introduction of the project and the user story of this project

Every time you have a report please put your name, a title for the report, the name of the costumer and in the description use Agile to ensure quality/readability of the report.

For Most projects developers and business managers will use User stories to report to costumers.

Here are some requirements for user stories:

1. Role: Who needs the feature/ Who is working on this project? ( customer, admin, developer).

2. Goal: What action/outcome does the user want?

3. Benefit: Why is this valuable?

For developers, there may be some instances where they need to provide proof of work through code reviews and 360* degree review from a colleague.

Here are some requirements for user stories:

1. Role: Who needs the feature? ( customer, admin, developer).

2. Goal: What action/outcome does the user want?

3. Benefit: Why is this valuable?

Here are some requirements for Developer-focused reports:

• Progress

  - **Delivered**: [List completed user stories].  
  - **Blockers**: [Bug #123, PR #456].  
  - **Next Steps**: [Prioritize tech debt].  

• Proof of Work (File upload/links):

  • Nextcloud screenshots (CI/CD logs or Deployment proof).

  • Git PR/commit links.