commit 6cd6d9aee66dbe321a32ac8098be5b016a94c323 Author: Christophe Vila Date: Wed May 27 14:28:44 2026 +0200 initial release diff --git a/CLAUDE.md b/CLAUDE.md new file mode 100644 index 0000000..4c04952 --- /dev/null +++ b/CLAUDE.md @@ -0,0 +1,18 @@ +# Context + + + +# Project Specification + +i need a flow chart representing a global request management system towards our agile devops teams. +our devops teams are responsible for : +- perform discoveries on initiatives (in adequation with enterprise strategy). once discoveries are done, an implementation plan is available with roughly quoted epics and features +- implement epics and features during program increments (meaning there are PI plannings where we commit a set of epics and features for each involved team) +- help operation teams to setup pilots (aka identified customers that will use the newly implemented features, which allow teams to get first feedbacks and perform obvious bug fixes before generalisation) +- perform level 3 support activities (for example, issues root cause analysis) +coming requests could be : +- a customer need pushed by project leaders for existing customer. a customer need is often already described as a feature expectation instead of a problem definition. +- an incident pushed by incident manager or support teams when confirmed through L1/L2. this does not concern urgent incident (that has a particular procedure allowing to directly impact agile teams sprints) +- support to deployment and operation teams. this covers all installation & configuration requests to ensure a proper service, usually when documentation is not enough (or not read). objective is to reduce agile team disturbance. +- request from customer success managers, mainly the anti-CHURN and business growth requests (so not really particular customer needs) but like an internal backlog of things to improve the product +the schema shall represent the different kind of requests with identified owners, these requests go through a common interface,