How we do it

/How we do it
How we do it 2017-11-03T08:06:12+00:00

Our process

In arqitekta, we think that it is important to take a process driven approach to IT projects, to ensure the quality of our work and to be able to scale our design effort to the largest programs in the industry.

We stand on the shoulders of giants and base our design process on the decades of trial-and-error at the big organizations that we have worked for.

Why not agile?

Whereas modern application development projects are increasingly using agile processes, such as Scrum, most infrastructure projects lend itself nicely to the classic waterfall model.

Theoretically you could use a scrum-like process but that would require you to build a lab containing all possible permutations of hardware and software components for you to use while brainstorming and using sprints, which of course is not feasible for most scenarios.

Instead our process is inherently waterfall-based with ideas taken from Kanban.

Architecture engagement (AE)

Storyboard (SB)

Logical design (LD)

Physical design (PD)

Architecture engagement (AE)

Storyboard (SB)

Logical design (LD)

Physical design (PD)

Kanban approach

It is important to honor the waterfall nature of this process, which stipulated that sequence of the documents should be maintained. Thus, the logical design shouldn’t commence before the requirement capture phase is completed, as well as the physical design cannot be done without a completed logical design.

This means the project focus will be to ensure that these deliverables are produced in a timely fashion, to the right level of quality and in sequence.

Cost of change

The described process puts an emphasis on the activities early on in the life-cycle of a project or program, it is ‘front loaded’ so to say.

This is done for the simple reason, that if you get things wrong early on in the project life-cycle, by negligence or lack of experience, then you run the risk of having to make fundamental changes further down the life of the project.

The further you move through the life-cycle, exponentially bigger the cost of change becomes.

By front loading the effort, the entire effort gets smaller and the risk of failure gets reduced dramatically.