PODC – what do managers do ?

PODC : Plan, Organize, Direct, Control

Managers plan, organize, direct, and control resources to achieve specific goals.

  • In planning, they set goals and determine the best way to achieve them.
  • Organizing means allocating resources (people, equipment, and money) to carry out the company’s plans.
  • Directing is the process of providing focus for employees and motivating them to achieve organizational goals.
  • Controlling involves comparing actual to expected performance and taking corrective action when necessary.

Source : http://2012books.lardbucket.org/books/exploring-business-v2.0/section_10_01.html

Rapports publiés : Etude d’impact du livre électronique en Fédération Wallonie-Bruxelles

Les Rapports de l’étude d’impact du livre éléctronique sur les librairies et bibliothèques de la Fédération Wallonie-Bruxelles ont été publiés par la Fédération  ce 28 Juin 2013:

What is a governance ?

What is a governance ?

First a governance must have a goal, we call it the VISION.

At the center of the governance, there are a set of RULES.The governance processes provide rules to  the “governed processes”.

Once the GOVERNANCE is defined, one must think about :

  • the COMMUNICATION of the governance
  • the EXCEPTIONS and APPEALS that can apply to the governance
  • the COMPLIANCE aspect : how to verify the governance rules are applied  ?
  • the VITALITY : when and how do we change the rules ?

Let’s think about a sample governance that we all know :  the road code.

  • The vision is that without a road code, the roads would become too dangerous.
  • The road code is the governance, the set of rules, for driving a vehicle.
  • The road code is communicated when you pass your driver license and via road signs.
  • There are some exceptions to the road code, for example for the police and ambulances. You can appeal if you can prove that you were in an emergency case.
  • Police controls are there to verify that you comply to the road code
  • The road code should be revised from time to time. The vitality of the road code is ensured by the authorities.

The Enterprise Architect

I just finished a slideshow about Enterprise Architecture for People&Technology.

Here is the contents of the last slide.

The Enterprise Architect:

  • Must have rather complete profile:
    • Understands the business
    • Knows the strengths/weaknesses of the complete application portfolio
    • Understands the technology required to succeed
  • Can compensate (nobody is perfect) if
    • Has an open mind and is creative (thinking out of the box)
    • Can communicate
    • Is eager to learn (business, applications, technology)
    • Establishes a method for documenting (or rather painting: architecture is an Art) the 3 architectures layers and their relationships
    • Is capabable of abstraction, can combine top-down, bottom-up and middle-out problem resolution techniques.
  • Can explain the gap between the current and the future architecture and propose concrete, actionnable transformation roadmaps
  • Can try to promote ICT architecture best practices (TOFAG, UML, ITIL…) at the business level but it’s not always a good idea (Ex: ICT Vs legal description of a product or service). Over an ICTer, I prefer someone who knows the business and has methods to document it in a structured way
  • Is a maestro at the service of the CEO : you are looking for Leonardo Da Vinci

Php to UML with bouml

For our startup, we have coded many classes in php. As the code grows, it becomes difficult to have a good overview of all the attributes and methods.

I tested yesterday bouml (that I had for long time on all my machines) to reverse enginner the code. The result is fast and efficient. I now have a nice uml diagram with all my classes.

Scenario evaluation with the 5W2H

When trying to determine the best TO-BE architecture, it can be useful to describe future scenarios. Each scenario can be described by the 5W2H method : Why ? What ? Where ? When ? Who ? How ? How much ? (QQOCCP in french).

You can then discuss the pro/cons as well as the obstacles and pre-requisites of each scenario. Once you know the preferred scenarios, it’s easier to draw the target (TO-BE) architecture.