Coming back to the Top-down (systems) design

The top-down design principle does more than identify poor practice. Accordingly, a system design effort should start by identifying the constituents for which the organization must produce outcomes, and that those outcomes are. It is from this work that the purpose, or design point, of the organization should be determined, not from an analysis of the company's existing capabilities. As a result, the design is "purpose down" rather than "capabilities up". (Haeckel)

This assertion from Haeckel is certainly true in project management. When determining what has to be accomplished at the end of the project (like the major deliverable or project result), most of the time, a lot of stakeholders propose some additional features and some 'nice to have' points. This is where the budget gets lost and where the problem are coming from.

Comments

Post a Comment

Popular posts from this blog

2023, the year of tackling your technical debt ?

Image
  Now that the year has started, it's a new dive in the day to day business, running from one client to another, shifting between priorities and deadlines. And what strikes me this year, besides the energy crisis (and the IT CIO costs cut paired to scarce resources), inflation, climate crisis, the Ukrainian war, it's the motivation to change the current status. Let me explain. Now that the majority of budgets has been granted, there is the recurrent pressure to 'do more, with less' (less people, less time to execute or to test, less money to get things done) and a need to address the legacy situation within IT departments. Tackling the legacy (being the old systems and solutions, already obsolete or nearly out of date) is not a walk in the park. You need to get an accurate inventory of what you have in prod (back office, front office solutions, hardware, storage, security solutions, development frameworks, security solutions, language used to code...or even your project
Read more

Happy New Year, folks!!

Image
Time to move on, to pause and to reflect on what has been achieved during 2022. In a nutshell, we made this year a subtle mix of management consulting projects (heart of Brussels, regional administration), a second-level of Open Group certification in Enterprise Architecture and, during the last part of the year, we designed a specific approach for managing what is called technical debt . The concept of technical debt is broadly detailed online, but concretely, it addresses all the legacy, the old code, the old technologies a client might have in his IT ecosystem and that need to be updated to new IT norms (code language, software versions, security levels etc.) A quite funny journey 😅 On our recruitment side, Magma filled every client request with a new candidate and quite great profiles were recruited. Congrats to our partner Delphine that made that amazing job! And, last and certainly not least, we hired 2 people for Blue Soft Belgium, bringing the team to 4. And this is a first y
Read more

Autumn restart

Image
It has been a while since the launch of Blue Soft in Belgium (yes, we started in April!! Nearly six months already 😨😨😨 and yes (thanks for asking!), the business is doing good. We had this new venture started, but we also boosted our Magma head hunting pillar that was literally exploding during the Spring and the Summer. Several profiles we identified for our clients, in the automotive and industry sectors, offering new positions and new career changes to our candidates! Congrats to all of them and good luck with your new endeavors!! And as from end of August, we will continue to work within the Public Sector, through our NTT Belgium collaboration. A lot of fun (and heavy work) yet to come...
Read more