Tag Archives: development process

More than a month from its start, the STAR adventure is in full development, and the 30 high school students passionately keep working on the software applications. We are happy to see that the Scoala de Valori and 1&1 project has had such a success with the youngsters and has been so very welcomed by all the participants!

My first grasp of the toxicity level for a project template was many years ago, during a meeting (which, taking into account the fees of the participants, wasted more than 2000 Euros per hour), its topic being the template (with capital T) about to be used for gathering some trivial piece of information. Should we keep the X area? It doesn’t seem to apply in our case … I say we should; if it’s there, we might need it. Let’s leave it as it is and we’ll figure out what to write there. And so on and so forth, hour by hour. No wonder this type of experiences make the practitioners want to run away (when can we work if we sit in meetings all day long?) only when hearing about project management. The problem is that the opposite – anarchy – is just as bad as a strict setup.

If by Project Management Professional (PMP) we understand a la carte project management we now have the question of the century!

But what’s the difference between them to begin with?

I’ve asked myself this question a while ago, when preparing for a combined course (Agile and PMP), and was surprise to find myself lacking any convenient answer. I’ve searched the internet and found an interesting distinction between them: while PMI is a standard, Agile is a framework. You may find the complete article here: Difference between PMP, PRINCE2 and Scrum/Agile.

In May 2012 a new team started working in Bucharest, its purpose, supporting Development Hosting teams with application operations on live and pre-live systems (deploying new patches and releases, performing regular maintenance checks, configuration updates, application monitoring, on call support for incidents) while acting as a buffer between Development Hosting teams and IT Operations teams on system related matters. The new team’s name was Operations Hosting Romania (OHR), a little brother of the Operations Hosting team from Karlsruhe.

Unit tests are not like wine. They do not get better with age. If ignored long enough, they become futile and stray down to the outskirts of code society. This is a diluted reference to unit test maintenance during development. But in order to understand exactly how unit tests work, we first need to slightly touch the topic of vinification.