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.
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
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.