methodology

How to build a Roadmap – Prioritize (Part II)

by

This post continues an earlier discussion about how to use the results from steps 1 – 3 to prioritize the actions we have identified to close the gap or difference (delta) from where we are to what we aspire to be. This is usually driven by evaluating the relative business value AND the technical complexity, plotting the results in a quadrant graph using an Action Priority Matrix. Other complimentary methods are discussed to help IDENTIFY what is feasible and what has the highest business value balancing business need with the capability to execute.

How to build a Roadmap – Prioritize (Part I)

by

This post discusses how to use the results from steps 1 – 3 to prioritize the actions we have identified to close the gap or difference (delta) from where we are to what we aspire to be. This is usually driven by evaluating the relative business value AND the technical complexity, plotting the results in a quadrant graph using an Action Priority Matrix. What we are doing here is IDENTIFYING what is feasible and what has the highest business value balancing business need with the capability to execute.

What is Natural Language Processing?

by

Before proceeding with the Building better systems series I thought I should write a quick post over the weekend about the underlying Natural Language Processing (NLP) and text engineering technologies proposed in the solution. I have received a lot of questions about this when I posted How to build better systems – the specification.

How to build better systems – the specification

by

We probably can all agree that defining functional and non-functional requirements are the most critical elements of a project’s success or failure. Reducing specification requirements errors is the single most effective action we can take to improve project outcomes. The approach I propose is inexpensive and mitigates much of the risk associated with defects and errors early in the development life cycle.

How to build a Roadmap – Gap Analysis

by

This post will discuss how to develop a robust gap analysis to identify any significant shortcomings between the current and desired end state. We use these findings to begin develop strategy alternatives (and related initiatives) to address what has been uncovered. The intent is to identify the difference (delta) from where we are to what we aspire to become. This exercise is critical to identify what needs to be accomplished.

How to build a Roadmap – Define End State

by

This post will provide a little more exposition and insight into one method I have found useful in practice for quickly defining desired end states. Done well, it can provide an honest and objective look to successfully understand where we truly want to be as an organization and face the uncomfortable truth in some cases where we need to improve.

Metaframeworks in practice, Part 2: Iterative-TOGAF

by

What methodology-frameworks do we need for broad-scope enterprise-architecture in a human-services government-department? This is the second of five worked-examples of metaframeworks in practice – on how to hack and ‘smoosh-together’ existing frameworks to create a tool that will help people make sense…

How to build a Roadmap – Define Current State

by

This post will provide a little more exposition and insight into one method I have found useful in practice for quickly defining current state. Done well, it can provide an honest and objective look in the mirror to successfully understand where we truly are as an organization and face the uncomfortable truth in some cases where we need to improve.

Enterprise-architecture is wicked

by

How do we cope with the wickedness of enterprise-architecture? I don’t mean here the implicit wickedness of people promoting term-hijacks and other half-baked notions as ‘the truth’ of enterprise-architecture – though heaven-knows there’s enough of that wickedness around. I also…