Benefit Review template

This template can be easily used for incremental approach in Agile style. In essence it helps to define the properties that will form the conditions of the functional tests. From my experience, this is essential for designing the “proof of concept”, it is especially true for the architecture (e.g. workload). [...]

Automation, humility and templates

There is a very amusing (and amazing as well) post about the seven capital sins of using automation for testing. In my yesterday’s post, automation had a huge importance. Therefore, the indications suggested by Colin, are to be taken with the utmost care.

In essence, the best solution against mistakes remains a good [...]

Gaining on data quality

The automatic data collection, based on a well designed unit-test (see this post ) needs the following steps:

A sound architectural design where services are neatly conceived for managing values and entities.
Collection requirements including boundary values (see Boundary values ). Thereby, the tests will be focused on the “critical” scenarios.
Developers able to work in a TDD [...]

Soft: gloves and fists

In my experience, finding the reasons of the problems (delays, poor output quality etc.) is not very difficult. Usually, the easiest symptom to spot is the gap between people and the rules they [...]

Iron triangle – Prince2 templates

The news about the killing of the “Iron Triangle” from the PMBook new edition (see post) has had the positive impact to clearly understand where to put the quality, among the existing constraints (Time, Cost and Scope).

Quality, from my understanding, can be viewed only as essential property (adjective) of the scope.It could be considered as [...]

Risks and leadership

Setting a new PMO is a different “sort of project”. It is a standard, perhaps a little worn statement that cannot be ignored. The diversity is made by many factors; the most striking one is the nature of the stakeholders. Often their weighting their biases toward the project are not easy because of the intimate nature of their expectations and doubts. At the end of the day, they are the most important part of the [...]

Risk – lack of “personal” awareness

“People living in glass houses cannot throw bricks”

Therefore, there is “my” interpretation of the Emotional Intelligence tenets:

Self-awareness
“Am I conscious of my usage of the rules? This consciousness implies the ability of gauging the receivers’ acceptance of our “message”.
It could range from hiding behind the role, from bending the rules in order to gain some points.
Self-management
“Have I evaluated the required effort/skills for maintaining the promise?” The negotiation is useful for its opportunity to gauge the counterpart’s interest on the topic. With no metric to measure the goal, it is almost impossible to have a shared evaluation of results.
Relationship-management
Once my part of the deal has been assessed, “am I able to involve the other people? This needs that everyone accepts – at least – the previous rule.
Social-awareness
“Do I know the written and unwritten rules before to start any other activity?” The power of the “fait-accompli” (already done things) exists only if the others can reckon our done. This means to share the same set of metrics. [...]

Quality importance in report

A workplace is an ideal fabric woven by rules. Some of them are clearly set (taking the form of documents – e.g. RACI) others are to be read in each person behavior. The latter are much more important. It is amazing how much information can be retrieved just asking for them with no other intention that understand the person’s [...]

More on reports

The projects are set up for delivering a product. Therefore, all the efforts are sustained for obtaining that specific result. The PM(O) must be able to supply, to the Snr Management, the information needed for evaluating whether the project is still feasible (i.e. within the scope, the delivery date, budget and quality) or not.

From this viewpoint, all other information (upcoming results, risks and issues) can be better understood in order to take action whenever it would be [...]

Managing the “weekly” (highlight) report

The most common tool for communicating with the stakeholders (outside the team) is the report. The quotation made by Von Clausewitz can be applied to many occasions.

There are several reasons for this, they span from excessive expectancies about the ability to produce information within the quality standard, to the lack of agreement about what it is worth being read (or viewed, when presentations are included). This post is dedicated to frame reports within the stakeholders’ management (the “Communication Management Strategy Report” has been published just today under Prince2 [...]