You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
Introduction of an idea to the Expert Group/Committee
Development of a concept from a business perspective (domain knowledge!)
Evaluation of the business value of the concept
Integrating the concept into the "big picture" of existing concepts
Development of a solution architecture
Development of further technical requirements, such as dependencies/acceptance criteria
Feature Proposal.
The text was updated successfully, but these errors were encountered:
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
The text was updated successfully, but these errors were encountered: