The “What”
The concise description of a human endeavor, which captures user story(s), workflow(s), feature(s) or capability(s) required to satisfy said endeavor.
The “what” is most often articulated by functional practitioners.
The concise description of a human endeavor, which captures user story(s), workflow(s), feature(s) or capability(s) required to satisfy said endeavor.
The “what” is most often articulated by functional practitioners.
The timespan between the moment that a need has been defined for a human endeavor (the “what“) and the moment that technology has been fashioned (the “how“) to serve that endeavor. The “when” is most often executed by sequential practitioners.
The justification for embarking upon an organizational development effort (i.e. to work on the business), which determines the resources and priority allocated to the breadth (the “what“), depth (the “how“) and the urgency (the “when“) of delivering a solution. The “why” is often driven by a combination of stakeholders, including functional practitioners, visionary practitioners and…
The fashioning of technology using machine language, programming languages or infrastructural configurations to serve the utility of a human endeavor. The “how” is most often executed by technical practitioners.
What we mean with we refer to “working IN the business…”
The 4P’s refers to projects, products, programs and portfolios in IT
What we mean when we refer to proactive effort