Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Different topics from open planning ⇾ “Business Perspective” #6

Open
stephanbcbauer opened this issue Apr 12, 2024 · 1 comment
Assignees
Labels
documentation Improvements or additions to documentation

Comments

@stephanbcbauer
Copy link
Member

What

Working model lacks business perspective/conceptualisation

The Working Model - Process Organisation is supposed to describe "From Idea to Release" - but starts with the first process step "Feature-Proposal", with concrete software development specifications!

It does not describe how a fixed idea becomes a feature with an elaborated concept, high business value, technical dependencies and known risks!
And the high standards discourage contributions and cause a lot of frustration!

Possible solution

Define clearer roles

  • (Domain-specific) Committee - overview of the "big picture" of concepts and vision; alignment
  • Expert Group - technicality; development of business concepts; assessment of business value; prioritisation
  • Architecture Committee - support with solution architecture; technical dependencies
  • T-X Committer / "development consortium" - development activities; implementation

Develop additional process steps

  1. Introduction of an idea to the Expert Group/Committee
  2. Development of a concept from a business perspective (domain knowledge!)
  3. Evaluation of the business value of the concept
  4. Integrating the concept into the "big picture" of existing concepts
  5. Development of a solution architecture
  6. Development of further technical requirements, such as dependencies/acceptance criteria
  7. Feature Proposal.
@stephanbcbauer stephanbcbauer added the documentation Improvements or additions to documentation label Apr 12, 2024
@jSchuetz88 jSchuetz88 transferred this issue from another repository Jun 12, 2024
@Grand-Thibault
Copy link
Contributor

@stephanbcbauer is this issues still relevant?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

2 participants