Customers running yellow projects have an out-of-the-box dev lifecycle prototype to review, try out and request additional support for.
User Problem
Urgent Demand: One of the first architectural decisions is to figure out how the development lifecycle works. Customers need an answer
Product Vision:: The product vision of the Web Modeler's process development lifecycle is communicated through slides and personal contact, but is not apparent through the product itself
Requirements Discovery: Gathering requirements for well-informed design and product decisions is time-consuming.
Release Notes
The Web Modeler is building a lightweight, out-of-the box development lifecycle to enable business users to review changes, promote them through changes, and maintain visibility into their journey
User Stories
The use cases and their stories are listed in chronological order. Build order is in parentheses.
Setup (4th)
[ ] (M) [Dev Env] When I create my process application, I want to select a cluster for development so I can simplify my deployment experience (slice of https://github.com/camunda/product-hub/issues/183)
Versioning (1st)
[x] (M) [Bulk Version] As a process developer, I want to create a version of my process app so I can start to move it through my deployment pipeline (slice of https://github.com/camunda/product-hub/issues/2016)
[ ] (S) [Microsurvey] As a user, I want to share my feedback about the OOTB PDLC so it can be improved based on my needs
Implementation Notes
The goal is to offer a happy path with minimal investment without consideration of edge cases or customization
The OOTB PDLC can be enforced through permissions (only some users can deploy or review), process (one step must be followed before the next), or transparency (each step is logged).
Recommendation: Provide transparency through comments on the main process, and lightly enforce process by providing primary CTAs that drive the user towards the "next step"
This should be delivered with an experimental mindset. These solutions are >70% likely to be rebuilt "properly" in the future based on the feedback generated through this
If the microsurvey can be worked into the experience early, then we can iterate on the initial iterations before the Self-Managed 8.6 release
Value Proposition Statement
Customers running yellow projects have an out-of-the-box dev lifecycle prototype to review, try out and request additional support for.
User Problem
Release Notes
The Web Modeler is building a lightweight, out-of-the box development lifecycle to enable business users to review changes, promote them through changes, and maintain visibility into their journey
User Stories
The use cases and their stories are listed in chronological order. Build order is in parentheses.
Setup (4th)
Versioning (1st)
Change Review (2nd)
Promote (5th)
Misc (3rd)
Implementation Notes
Implementation Timeline
Follow-up Issues / Out of Scope
:robot: This issue is automatically synced from: source