Ruben Vuylsteke


Recent Posts

Just enough architecture in an agile transformation

By Ruben Vuylsteke on 03 April 2018

Companies are currently in the middle of a major digital transformation. Being able to quickly respond to new customer needs and expectations is crucial. Consequently, project teams are being organised differently. For example, more and more SCRUM teams are being put together to provide software more agilely. However, a question I’ve been asked by customers repeatedly concerns the place that architecture must be given within this story. My opinion is that a minimum of architecture is always necessary. Just enough, just in time. In this blog post, I want to illustrate a technique, based on a previous project, that lets you gain a helicopter view with a minimum amount of enterprise architecture, which is something that is unarguably adding value for a company that is going through a complex transformation.

Continue Reading

3 Valuable Business Analysis deliverables that lead to project success

By Ruben Vuylsteke on 14 January 2016

If you pay little to no attention to business analysis, you'll often find yourself making the wrong assumptions during the solutions phase of a project.

Continue Reading

Why every project needs a benefit map

By Ruben Vuylsteke on 07 January 2016

A common issue encountered on projects is that the project goals have not been clearly defined. A Benefit Map is a powerful visual to provide solace.

Continue Reading

Bring your stakeholders together for a story mapping workshop

By Ruben Vuylsteke on 18 June 2015

Recently, I participated in an agile business requirements training given by my colleague Thomas De Vries and Patrick Steyaert. One very interesting technique that they highlighted is story mapping. In this post, I will explain how to apply this technique and highlight the advantages compared to traditional techniques for eliciting requirements.

Continue Reading

4 Tips for writing business user stories

By Ruben Vuylsteke on 16 June 2015

Business and IT speak a different language. This is a challenge for many organizations as it hinders communication about requirements in IT projects. An often suggested way to deal with this problem is to use the simple and fixed format of user stories to express requirements (as a..., I can... so that ...) and I fully agree on this. However, as a business analyst, I notice a lot of confusion among business people when it comes to the definition of a user story. I often hear that user stories are too technical for them. In this blog post I provide 4 tips to write user stories that express business requirements making sense from a business point of view.

Continue Reading

Lists by Topic

see all

Posts by Topic

see all