The Deadline – Chapter 11

--Originally published at Coder Bebop

Now it has begun unfolding: the real plot of this book, the real threat that the author wishes to show us, and it is *drumroll* politics. To be more precise, and to quote the book, pathological politics. And I find this interesting, because I have always seen politics as an attempt to organize all the resources in a country (or a big organization), so we may say that it is management on a great scale. As the characters discuss: what they are trying to build is politics, organizing people and moving them towards a goal. Belok’s practices are those of destruction and mischief, since he just wants to screw around and take all the credit for himself.

Something interesting that came from a character whom I did not excepect too much participation from was General Markov. When the trio are discussing their strategy to keep up the production and sidewind the NNL’s best, he says something that I think describes what this book’s core is made from: “Remember we are here to work hard and learn.” Nothing that our characters have done until now matters until the final product is achieved and they get the results they want from their experiments. The only way that our characters will fill their roles is by working, their obstacles are the very people in charge of them. I wonder if this will go full “Animal Farm” with the workers revolting against this one douche.

It is a shame when not everyone involved in a project is on it for the purpose of doing said project, but rather stalling all the work for their own benefit. I suppose it is much quicker and easier to let others work and get all the profit, but it never ends well.

The Deadline Chapter 10

--Originally published at Coder Bebop

So basically this whole chapter consists on:

Mr. T (finally!) ensuring he is being payed for his time, effort, and masterminding of turning a nobody-company into a billionaire enterprise (strangely enough, he does not mind adding “kidnapping” to the payment list) in two years.

Him meeting and discussing about management guts with Abdul Jamid to talk about guts and do a model on Mr. T’s guts (which sounds weird outside of context).

That’s pretty much it for this chapter. Very few things happened, yet it took 21 pages to get to the point: there is a way to measure guts if you apply the principles of divide-and-conquer and take every piece there is in a hunch, a small reason behind that decision. A gut is basically made up of this teeny reasonings which you cannot feel, but putting all of them together gives off a strong resolve to act in a certain way.

I liked the example used by Dr. Jamid in which doubling the size of a team makes it even less productive. It is weird how Mr. T can describe little by little how he would decide not to do this, but the guy has no idea whatsoever why he would make that call. But is this practice even possible in real life? Is it a thing which I have never heard about before reading this book? My guess would be that this is some high-level reasoning in the management business. And like a joke from another country that I could not understand, this is probably something management professionals have longed to attain and regular people do not have knowledge about, mainly due to lack of experience. Perhaps that is the reason why I did not find this chapter that much interesting.

Not that gut, though…

ONLY 750 DAYS TILL D-DAY!

--Originally published at Blog de Célia

In these news chapters we meet to new characters: Dr. Rizzoli and the ex-general Markov. Mr. T met Rizzoli because he is a world know risk manager, he asked him some advices to determine how to manage the risk and how improve the productivity in his future projects. The Tompkins met ex-general Markov since he thinks he will need him in the realization of the projects.

Mr. T lessons from his discussion with Dr. Rizzoli

To my opinion, the most important learnings that Mr. T had during his discussion with Dr. Rizzoli is that productivity improvement comes from long term investment. You can’t improve your productivity by fixing stuff with short term solutions. The work has to be thought in a long-term vision to really improve the quality of your production chain or of your teamwork. It means as well that it’s better to keep your team together when they work well (see the paragraph about the meeting with Markov), because they will get better together.

Then, the other learnings are about risk management. As Mr. T wrote “assess each risk for probability and likely cost” and “Track the causal risks, not just the ultimate undesirable outcomes”. I think that managing risk in a project can be really hard, because first you have to think to every risk that can occurs. These lessons, that Mr. T learnt about risk management make me think to the pareto principle that says that for many events, 80% of the effects come from 20% of the causes. I learnt this principle in my studies in my first year of two year degree (a few years ago, time flies, my teacher of project management told us that we have to look for the 20% biggest risks that could happen in the project to avoid 80%

Continue reading "ONLY 750 DAYS TILL D-DAY!"

Review on Chapter 10 of “The Deadline: A Novel about Project Management”

--Originally published at Project Evaluation and Management Reflections

The Hidden Treasures of System Dynamics

While Mr. T. is in Rome to check if Morovia actually does pay him as they had promised (yes, he´s apparently still suspicious and he still cares about the money, despite the fact how much he obviously likes his new job), he gets to meet Dr. Abdul Jamid, an acquaintance of an old friend. Dr. Jamid is working on management dynamics, something that will prove helpful for the tasks to be done in Morovia…

When first looking at the functionality of management dynamics, Mr. T. is overwhelmed by all the information and reluctant to acknowledge the usefulness of modelling management dynamics… something I can relate to better than anyone, after completing a whole module on system dynamics in my previous semester at university.

My professor back then introduced us to system dynamics with the classic „Chicken & Eggs problem“.
If we think that no other variables other than chicken and eggs exist, we have a system consisting of one reinforcing loop, that is „More chicken 🐔🐔“ –> „More Eggs 🥚🥚🥚“ –> „More Chicken🐔🐔🐔🐔“ –> „More Eggs🥚🥚🥚🥚“ …… (you should understand it by now)
This would lead to exponential growth in the stock of chickens…however, in reality, growth is limited by a certain carrying capacity, e.g. the size of the farm where chicken live. At one point, the farm will be full and chicken will start crossing the road next to it – which inevitably leads to lots of 🍗🍗🍗 🍗 (dead chicken 😢). This actually represents a new feedback loop, which is balancing the total stock of chicken.
Depending on variables such as growth rate, death rate, carrying capacity and time delays, the total number of chickens could take different sizes over time.

Check out this post by

Continue reading "Review on Chapter 10 of “The Deadline: A Novel about Project Management”"

Review on Chapters 8 and 9 of “The Deadline: A Novel about Project Management”

--Originally published at Project Evaluation and Management Reflections

Chapter 8 – Welcome to Latvia

After having selected managers for his teams, Mr. T. now faces the task of designing his Project Management Laboratory. Learning from the lesson in the previous chapter, Lahksa is proposing to involve a consultant, as none of them has ever done anything similar before. According to her, a consultant should be involved for „unusual, highly specific need[s]“ – somebody should tell that German politicians, because the Ministry of Defense alone spent more than 200 million euros on consultants

For this reason, we get to meet Dr. Hector Rizzoli, whom Lahksa „invited“ to Morovia. Actually he is supposed to be giving a speech in Riga, Latvia, but with her connections Lahksa organized for him to be dropped off in Morovia, where they simply pretend it´s Latvia. He appears to be a nice man, but clearly a little bit dreamy as well, as despite all small hints and discrepancies he just doesn´t realize he isn´t in Riga. Not only does he seem to be a nice person, but when Tompkins casually mentions that he is running some experiences, he instantly gets excited – prove enough that he should be the right man for the job. When he designs with Mr. T. and Belinda the experiments later on, his approach is quite simple:

For each project, they had a single, designated learning goal, a
particular effect that the relative performance of the competing
teams would help to prove or disprove.

So instead of asking many questions and trying to vary/conclude/include/exclude a lot of factors, simply one goal is defined that will serve to compare the performance of the different teams.

In the chapter, we can also learn from Dr. Hector Rizzoli a few lessons about managing the experiment of Mr. T. and projects

Continue reading "Review on Chapters 8 and 9 of “The Deadline: A Novel about Project Management”"

Risk happens

--Originally published at TI2011 – Press enter to continue…

Today in the fabulous adventures of Mr. T, he will be accomplice on the abduction of Dr. Rizzoli without the Dr. even noticing it. LATVIA WELCOMES THE EMINENT DR. RIZZOLIThe sign at the airport said And that's how the Dr. started helping on how to manage the experiment of management for Morovia. He helped with … Continue reading Risk happens

Productivity, Risk and Defense

--Originally published at TI2011 – DVant Blog

As Dr. Hector Rizzoli stated, there is no such things as a short-term productivity fix. In this chapter of the book The Deadline, one can learn first about the productivity improvement when doing project management. But for this case, Mr. Tompkins had to execute a perfect plan for "stealing" Dr. Rizzoli from his trip. This... Continue Reading →

Economics of Software Engineering

--Originally published at Project Evaluation and Management

Economics is one of the key values in order to generate a truly successful project.

The Software Engineering Economics is a complex subject, but it can be reduced up to five major areas: The Fundamentals, The Life Cycle Economics, The Risk and Uncertainty, The Economic Analysis Methods, and the Practical Considerations.

The Fundamentals refers to the principles of Economics, such as Finances, Inflation, Cash Flow, Taxes, etc.

The Life Cycle Economics refers to Economics related to the product itself, such as the Product Life Cycle, the Project Life Cycle, Prices, Costs, And some Investment Decisions.

Risk and Uncertainty refers to Goals, Estimates, Plans, Making Decisions taking risks and uncertainty under consideration.

The Economic Analysis Methods refers to what are you going to get in return for the project, things like Cost-Benefit analysis enters into consideration here.

And finally, the Practical Considerations refers to things you can do to make your life easier, such as Outsourcing, or taking the Good Enough principle into consideration.

These areas require further study, but in general, this is what they are.

Abdul Jamid

--Originally published at Project Evaluation and Management

During this chapter, Mr. Thompkins had the opportunity to meet an interesting character, Dr. Abdul Jamid, for his surprise, Abdul is recommended by his old boss Jay, and finally, he had the opportunity to talk with Dr. Abdul.

Abdul reached Mr. Thompkins with the purpose of teaching him an important tool for Project Management. This tool is called Modeling and Simulation.

In the book this works by using a software called ithink but of course, this software is not necessary for the concept. 

The concept of Modeling and Simulation follows a pipeline, the first thing you have to do is to Model your hunches about the process that gets work done, then you use the models to communicate and refine your thinking about how the process works. Once you have the model you simulate the results and finally you tune the model against the actual results.

This concept is important since it can be applied to lots of things, not just Project Management, in fact Machine Learning often uses this approach.

css.php