kriss/slot
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

update CLAUDE.md

Browse Source
This commit is contained in:
Christophe VILA
2025-09-04 13:01:01 +00:00
parent 0e2c377779
commit 759b17fc53
1 changed files with 32 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

32
server/CLAUDE.md Normal file
View File

@@ -0,0 +1,32 @@
# General information
This project will be used by following kind of users :
- program managers:
they manage a program, which encompass all activities allowing to reach a company objective. there are different kind of programs:
- strategic customer program: in this case, the program represents all the go-to-market activities for this customer (from pre-sales to maintenance)
- technical program: in this case, objectives are usually transversal and benefits for all products and solutions of the company. some examples: ability to deploy on public cloud, going from monolith to micro-services architecture, ...
- other transversal activities like innovation can also be run through a program
- product managers:
they manage one or several products, defining the feature set for each.
they design features to match needs expressed by customers in the pipe, as well as needs that should arise from future customers, based on market analysis.
they also decide if a given customer request has to be processed as a custom or through a product feature.
- business owners:
they decide strategy and priorities in case of unability to address all needs with current budget
- engineering managers:
they manage a set of agile teams in charge of developing the features.
their organization is based on SAFe principles, meaning they are committing their scope by program increments of 3 months.
Objective of this project is to provide a UI that would :
- help program & product managers to record their needs in term of new features or customs to implement in a product, based on priorities, expected start and end dates,
- help top management to have visibility on the overall picture (aggregation of all needs recorded) and have
This component is server-side.
Its aim is to provide API that would be used by UI whenever a core business logic has to be executed.
Core business logic is around computing start and end dates for each
# Technical constraints
UI written in React, using ShadCN UI
Backend written in Java, using Quarkus
# Features definition