Summary
With the latest V2 workflow (f3ce1b8), there are number of context switching and during "Ideation" and "Inception" phases
During the Ideation phase, there are some technical questions like programming language and web framework which is not related to business justification and requirements.
During Inception phase, users/audiences will make business decisions during "intent-capture" and then proceed to "practices-discovery" that focus mostly on technical perspective and how the team work. Then proceed to "requirements-analysis" to make business decisions.
And also "Application Design" will really dive deep into technical decisions, which is kind of too early and also partially overlapping with "foundation/scaffold" unit (which will be executed during construction phase). I also found that the information in application-design.md document will be outdated and no longer valid after we proceed to construction phase. The items that will retain are mostly programming languages/frameworks but the architecture, solutions and API contracts will be changed in later phases.
Motivation
Ensure the activities during "Ideation" and"Inception" will focus more on business first and gradually involve technical details/decisions later. And leave technical decisions to be discussed and implemented in "Construction" phase.
Detailed Proposal
- Avoid/Remove technical questions/decisions during Ideation/Inception phase
- Remove Application Design step and do the design during construction for foundation/scaffold unit.
- Rearrange the sequence of workflow
From
Practices Discovery -> Requirements Analysis -> User Stories -> Refined Mockups -> Application Design -> Unit Generation -> Delivery Planning
To
Requirements Analysis -> User Stories -> Refined Mockups -> Practices Discovery -> Unit Generation -> Delivery Planning
(Application Design got removed)
With this sequence, users/audiences will heavily focus on business and gradually work on technical decisions in later stages.
NOTE: I believe that we could consider refined mockups optional as well (potentially for workshop scope)
Alternatives Considered
Provide options to the user to navigate the workflow. This will add more complexity to the workflow code/instruction but improve usability to match what users' needs.
Drawbacks
Accept context switching during inception phase as this is part of AIDLC operating model where cross functional team will work closely as team.
Additional Context
No response
Summary
With the latest V2 workflow (f3ce1b8), there are number of context switching and during "Ideation" and "Inception" phases
During the Ideation phase, there are some technical questions like programming language and web framework which is not related to business justification and requirements.
During Inception phase, users/audiences will make business decisions during "intent-capture" and then proceed to "practices-discovery" that focus mostly on technical perspective and how the team work. Then proceed to "requirements-analysis" to make business decisions.
And also "Application Design" will really dive deep into technical decisions, which is kind of too early and also partially overlapping with "foundation/scaffold" unit (which will be executed during construction phase). I also found that the information in application-design.md document will be outdated and no longer valid after we proceed to construction phase. The items that will retain are mostly programming languages/frameworks but the architecture, solutions and API contracts will be changed in later phases.
Motivation
Ensure the activities during "Ideation" and"Inception" will focus more on business first and gradually involve technical details/decisions later. And leave technical decisions to be discussed and implemented in "Construction" phase.
Detailed Proposal
From
Practices Discovery -> Requirements Analysis -> User Stories -> Refined Mockups -> Application Design -> Unit Generation -> Delivery Planning
To
Requirements Analysis -> User Stories -> Refined Mockups -> Practices Discovery -> Unit Generation -> Delivery Planning
(Application Design got removed)
With this sequence, users/audiences will heavily focus on business and gradually work on technical decisions in later stages.
NOTE: I believe that we could consider refined mockups optional as well (potentially for workshop scope)
Alternatives Considered
Provide options to the user to navigate the workflow. This will add more complexity to the workflow code/instruction but improve usability to match what users' needs.
Drawbacks
Accept context switching during inception phase as this is part of AIDLC operating model where cross functional team will work closely as team.
Additional Context
No response