jfdeclercq.com Welcome Photos About Blog
Feedback Contact Twitter Facebook LinkedIn Downloads Lowas.be

- >> February 2020 >> - Show 10, 25, 50, All News - Expand All, Compact All, 1024 chars

March 2020

@JAVAUXM On doit tous se battre contre le covid, certains plus que d'autres. Je vous souhaite de le terrasser !
RT @KiwiEV: In Italy today, a priest decided to live-stream a mass due to COVID-19. Unfortunately he activated the video filters by mistake. https://t.co/zu2qwAlCyT
@BooXtream When you are a visionary, you sometimes need to wait for those who don't have a clue...
"And wouldn't it be nice to live together In the kind of world where we belong?"
An architecture is not only determined by its own functionality and performance, but also how it is integrated in its ecosystem. #entarch

February 2020

RT @RudyakMarina: What to do if you can't shake hands? #coronavirus #creativity #china https://t.co/MZ5aginwdD
"Embed your senior designer into the C-suite" : McKinsey Insights: Are you asking enough from your design leaders? https://t.co/XBVB5fJdoG

January 2020

On Monday January 13th 2020, I attended an event organized by Cyberwayfinder. The event thema was about the different types of architecture required to take care of business strategy, data, technology, security and risk in order to design a Digital Enterprise in a structured way.

The inspection process

At some point one of the presenters talked about an important process for Enterprise/Business/IT/Application Architects : the inspection of the delivery.

This is a well-known problem in IT projects: the target architecture is very often not respected for many good and bad reasons.

This raises the question of “inspection”. When do we inspect the work in progress as Enterprise Architects ? Do we have a mandate for inspection ?

Continuous or punctual inspection ?

We could imagine two types of inspection: continuous or punctual. The continuous inspection requires much more time but is maybe the only way in the context of agile projects…

What to do with deviations ?

At the end of an inspection, deviations could be identified. What can we do with such deviations ?

  1. We accept the deviation and re-integrate it in the “AS-BUILT” architecture
  2. We can ask an immediate rework because the deviation is not acceptable (e.g. bad implementation of security constraints)
  3. We don’t accept the deviation but we don’t force the immediate rework : we register a “technical debt”.

20 years ago, when Agile wasn’t born yet, we could be agile before Agile. For example by developing software using the DSDM method.

On the “The QA Lead” website you can find a nice description of the Dynamic Software Development Method (DSDM):

What is DSDM ?

"La beauté n'existe pas, elle est là ou on la voit. Et lui (Jean-Paul Gauthier), nous la montre." #france2 #le20h
@XenitECM @ucll_ict Question is : what confidence level is acceptable to avoid annoying process inefficiencies and confidentiality breaches ?
"Drink your own champagne" is better than "Eat your own dog food"
My 2 jArchi scripts (one new as I had forgotten to post it last year) #arcimate #archi ? https://t.co/XnFY4spHGF https://t.co/glgKYXIzzm

|| >> February 2020 >>