W5HH Principle

W5HH Principle

In project management for Software, there is a so called W5HH principle, to use for ensure that you cover the project rationale in a well though way. Why is the system being developed? What will be done by When? Who is responsible for a function? Where are they organizationally located? How will the job be […]

T Shape Competence Model

T-Shaped Competence Model

The T Shape model in general visualize the difference in competence in two axis. Either you are broad, an generalist. Drawn in horisontal axis. Or you are in depth very skilled within a specific area. Drawn as vertical axis. Why separate competence like this? Roughly, we want to say that the generalist work with strategy. […]

User Story

User Story

In a culture, normally agile, where there are product owners, the requirements is written in User Stories. To be frank, one argue that the User Stories is not requirements. They just describe what the product owner wants, at the moment the story is written. It’s prone for change, due to changed needs. The stories are […]

INVEST Requirements

INVEST

Similarly to SMART Goals, the User Stories within software development says to be INVEST. INVEST is a widely accepted (expected) set of criteria, or checklist, to assess the quality of a user story (common in agile). If the story fails to meet one of these criteria, the team may want to reword it, or even […]

SMART Goals

SMART Goals

S-Specific, this is the what, where, how when and with whom part of the goal. For example: I want to run the profit and loss report  M-Measurable, break down the goal into things you can measure.  For example: I will run the report every month  A-Attainable: Is the goal attainable? Will this goal be able […]

Ralph Stacey Matrix

Ralph Stacy Matrix

This framework partially touch the philosophical plane of assessing. It reach out for way forward to navigate, a solution or solving a problem. Ability to set a direction. Beside this matrix, it’s worth look into this guys (Ralph Stacey) history and other readings. This specific image of choice to describe the matrix is by no […]

V-Model (Software Development Lifecycle)

SDLC V-Model

This model might rather fit into a concept than an actual framework or methodology. Instead of Waterfall methodology where all phases go downwards, V shape expect a matching verification phase before allow to go on – resulting in phases being “cleared” iteratively in smaller work batches. Like waterfall, the model is quite strict and could […]

Agile

Uses an iterative approach to software development. Follows a use case/scenario driven requirements approach. Should be architecture centric. Is based on modelling visually Well-known agile software development methods include: Agile Modeling Agile Unified Process (AUP) Dynamic Systems Development Method (DSDM) Essential Unified Process (EssUP) Extreme Programming (XP) Feature Driven Development (FDD) Open Unified Process (OpenUP) […]

STAS – Sliding Technology Architecture Strategy

Sliding Architecture Strategy

The STAS is in the core about the reference architectures at an organization, or a unit within a large organization. This model help you set the path in on the strategy used today and what strategy it have to use tomorrow. There is still a thinking that a company or organization “have a IT strategy”. […]

BDN – Benefits Dependency Network

BDN - Benefits Dependency Network

For business valuation and development, there might provide a lot of insight to craft a BDN to get a overview of the situation. It can act as a map to identify what drivers cause some IT services to function or exist. A good BDN do differentiate external facing drivers from these who are internal facing. […]