“You’re a manager. A systems manager, and a good one” – Chapters 1 & 2

--Originally published at Meeting the Deadline

Sysadmin dogo founs in da Redditz: https://www.reddit.com/r/corgi/comments/e1ir21/tate_is_confused_about_his_new_sysadmin_role/

Welcome everybody, ladies and gents, to this great and profound adventure that is Project Evaluation and Management.

Today it’s indeed a great day, because today is the day we start to unravel the lessons learned from the journey of Mr. Webster Tompkins, a systems manager that, in words of Lahksa Hoolihan, is “a good one”.

Webster and Lahksa are essential part of The Deadline: a novel about project management, a book in which this post (and most of the following posts) is based. The book gives us a head start about what to expect in project management matters while covering the story of how a country in the third world carefully crafted a plan to create a world-class software factory and become the first in the world in export of shrink-wrapped software by the year 2000, which of course had its up’s and down’s.

We will be covering all the chapters in the book in posts containing from 1 to up to 3 or 4 chapters, leaving only the key concepts expanded and some key situations of the narrative. Also, from time to time, we’ll be covering extra topics outside of the book related to project management and business economics. More on that on future posts.

So, make sure you have with you paper and pen, notes and pencils, tablets and laptops, because you might want to take notes of some of this. Certainly, it is an insight of TOP SECRET information from one of the most profitable (I do hope so) venues of the Morovian Government.

Sysadmin dogo founs in da Twitters: https://twitter.com/nixcraft/status/770654517280989184?lang=ca

Let’s begin by describing how the life of a very talented systems manager (but unappreciated in his work environment) took a drastic turn, because Continue reading "“You’re a manager. A systems manager, and a good one” – Chapters 1 & 2"

Economics of Software Engineering

--Originally published at Project Evaluation and Management

Economic Engineering

Engineering economics is the application of economic techniques to the evaluation of design and engineering alternatives. The role of engineering economics is to assess the appropriateness of a given project, estimate its value, and justify it from an engineering standpoint.

Engineering Economy involves formulating, estimating, and evaluating the economic outcomes when alternatives to accomplish a defined purpose are available.

Engineering economics quantifies the benefits and costs associating with engineering projects to determine if they save enough money to warrant their capital investments.

General concepts

Efficiency: Efficiency of a system is generally defined as the ratio of its output to input. The efficiency can be classified into technical efficiency and economic efficiency.

Technical efficiency: It is the ratio of the output to input of a physical system. The physical system may be a diesel engine, a machine working in a shop floor, a furnace, etc. (Technical efficiency (%) =  Output/ Input × 100)

Economic efficiency: Economic efficiency is the ratio of output to input of a business system. (Economic efficiency (%) = Output/Input  × 100 = Worth/Cost × 100)

Interest: Money paid for the use of money

Investment: Is an asset or item acquired with the goal of generating income or appreciation. (Interest = Current Value – Original Amount)

Loan: Is money, property, or other material goods given to another party in exchange for future repayment of the loan value or principal amount, along with interest or finance charges. (Interest = Current Total Owed – Original Amount)

Interest Rate: Interest paid per unit time. (Interest Rate = Interest paid per unit time / Original Amount)

Rate of Return (ROR): Interest accumulated per unit time. (ROR = Interest accumulated per unit time / Original Amount)

Time Value of Money (TVM): Is the money available

Continue reading "Economics of Software Engineering"

Chapters 1 & 2 reflection

--Originally published at Project Evaluation and Management

The Deadline: A Novel About Project Management

Chapter 1

The first chapter is named Opportunity Knocking.

In this chapter the novel present Mrs. T to us, he is the ReSOE (Released to Seek Opportunities Elserwhere) of the Big Telephone and Telecommunications Company´s.

Mrs. T was a manager and the spy from Morovia was talking with him and she ask this:

“Let me answer that question with a question. What’s the hardest job in management?”
“People,” Tompkins replied automatically. He knew exactly where he stood on this subject. “Getting the right people for the right job. That’s what makes the difference between a good manager and a drone.”

I think that this was the most important part in the lecture because she was giving an opportunity to him and they start to talk about management. I think that the opportunities only present at once’s, Ann you have to make a good decision for that opportunity, not all the time opportunities arise in your life, so you have to take advantage of when you have one in your way.

They talk about “What’s the hardest job in management?”, He replied with people. This is the first time we see the word manager. I think the same, the people are the hardest job in management, because you have to choose the correct person. because people are the ones who do the work and if they are not happy or bring problems to work a heavy work environment is created

Chapter 2

The second chapter is named Standing Up to Kalbfuss.

In this second chapter they are like in a plane and Mrs. T dreams for a moment some things. Once you wake up. he starts talking to others and Kalbfuss tells him to teach them the hard science of management.

Continue reading "Chapters 1 & 2 reflection"

So, Software Eng. has Economics?

--Originally published at TI2011 – Alex’s Barn

As Engineers we create products, develop solutions. These projects not only (could) have a potential benefit for the society development and wellness of the people who would use our products.

From this idea, we could endorse an utopical image of the world, where our services are offered as a gift to the world, because, Who wouldn’t love being part of the progress of this society, impacting lots of lifes over decades or, even more, over centuries?

The world without money. Src: Imgflip

This sounds great, but it would be way better if we are paid for this.

The cruel reality is, we all need money. We all want money. People or enterprises, everyone is looking for money, making more and more profits. In this course we have to attach to this point of view. An Engineer’s work has value, it could be represented as a factual payment, each company deserves profits for their services. This thinking is healthy, because we deserve that paid for our services. This self-valuing thinking is responsible of all our Economy, for several centuries.

Settled our basis, let’s dive in Engineer Econ.

Source: giphy

A brief definition of Eng. Econ.

A whole definition I found about EE. Engineering economics quantifies the benefits and costs associating with engineering projects to determine if they save enough money to warrant their capital investments. Engineering economics requires the application of engineering design and analysis principles to provide goods and services that satisfy the consumer at an affordable cost.

Engineering economics involves the systematic evaluation of the economic benefits of proposed solutions to engineering problems. The engineering economics involves technical analysing with emphasis on the economic aspects and has the objective of assisting decisions.

Engineering economics is closely aligned with Conventional Micro-Economics. It is devoted to problem solving and

Continue reading "So, Software Eng. has Economics?"

Economics of Software Engineering

--Originally published at TI2011 – The Broken Wallflower

In this post we are going to talk about the origins of economics in software engineering, fist of all economic is a science that studies the resources needed to fulfill the human needs, this also includes the human behaviour, and engineering is the science that involves techonologies in the proffesional area. Saying this, economics in software engineering is a field who involves the basis of economics into technology systems.

This is a gif of a bar graph – giphy

At a first look it could seem that a software system may not require any economics knowledge, but that is not true, nowadays every system that is in the market requires a full in depht investigation about the market itself, one big example could be Uber, this system is similar to a taxi system, the only differences are that Uber provides a higher quality service, you get to choose the type of car that you’d like to ride in, and a few extra details that make your ride a lot better than riding a cab.

This is a gif of the Uber app- giphy

Lets analyze how Uber did to make it to a top system

First, the idea of making this system a real thing was to give users a better experience when trying to get to any places, provide a cheaper service and a safer service among the ones that already existed.

Second, establishing the market, unfortunately Uber is not made for everyone, eventhough everyone can hop into a Uber car, not everyone is allowed to use the system, there is an age restriction to use the system.

Third, places where the system would be more required.

Fourth, once competition starts showing up, what will they do to keep being number one worldwide

These are some of the thigns

Continue reading "Economics of Software Engineering"

Deadline Reflection Ch1-2

--Originally published at TI2011 – DVant Blog

I never expected to read a novel about project management. My first impression of it was that it has a creative approach to introducing important concepts of this topic in a smooth and intelligent way. The story in this first two chapters introduces two characters with very peculiar personalities and great perspective of the situation.... Continue Reading →

Deadline part 1 & 2

--Originally published at TI2011 – The Broken Wallflower

This is a picture of the cover of the book- Amazon

For those who doesn’t know what The deadline is, the deadline is a novel by Tom DeMarco published in 1997, this is one risky project because it tries to teach how does the software project management works using a novel as it’s conductor, the story is about a man who is kidnapped by an organization who is trying to reclute the best talents in order to become one big organization capable of developing world leadership systems.

During these posts we are going to disccus about the adventures that the main character faces during the book, and give our point of view about the novel chapters, with no further to say lets analyse chapters 1 and 2.

Part 1

For the fist part of the book the novel introduce us to an auditorium, where apparently there is a program that will teach the audience how to take advantage of the upcoming oportunities, and notice when an oportunity is given to them. The main character, Mr Tompkins, seems like he does not what to be there because as soon as the novel starts it tell us that Tompkins has ben asleep in the back seats of the auditorium for around an hour, where of couse he has been no been paying attention to the event, as soon as he wakes up the noticed that a well loking woman is sitting right next to him.

Mr Topkins starts asking the woman about the conference that is being given but seems like she does not what to talk about it, little did Mr Topkins know that this woman is sitting next to him for a reason, they are sitting so far behind that they are able to talk without interrupting the event, so

Continue reading "Deadline part 1 & 2"

Chapter 1

--Originally published at Erick learning experience

One of my first impressions while I was reading this chapter was that this book is going to be just theory and that stuff but when I start reading more the chapter was kind of funny, the most interesting was when Tompkins start talking with Lahksa Hoolihan about who was she and start talking about the importance of knowing who to kidnap, when she start talking like about that I start thinking about what I was reading and in my opinion if someone tell me that is kidnapper I would not accept a drink of that person but in the shoes of Tompkins it was a good idea because it was Dr. Pepper and most important it was a diet Dr. Pepper so why not?

Talking about more serious thing about the first chapter I agree in the part that one of the most important thing about a company is to get the right people but is one of the most complicated thing because get those persons is not cheap but is a crucial part to make a company a success.

Chapter 2

I start this second chapter hoping to know what happen to Mr. Tompkins and I agree with Tompkins that this chapter it’s like to be on drugs, becuase in my opinion they are explaining some important stuff in the manner of Project Management in a very strange but interesting way, the things that I keep as the most important of this chapter is the importance of bring attention to the people, teach them how to make teams, make them feel as part of the team, make sure they stay healthy, the importance of letting express themselves.

The Deadline Chapter 1 & 2

--Originally published at TI2011 – Alex’s Barn

Hi again.

After a cold winter holiday, bunch of hours of procrastinating personal projects, and working on two novels, I come back to school. New projects, new perspectives, new emotions.

This semester, I had to take the “Evaluation Project” lecture and, one of the goals is reading “The Deadline” novel, from Tom DeMarco. After a couple of pages, pop up a concept: P E O P L E.

The Deadline: A Novel About Project Management , Amazon.es

This made come into my head a story I experienced before.

The intern who learned manage people.

Last summer, during my internship, the host Enterprise made groups of 3 interns and formed teams with them. The main goal was each team had to develop their own mobile application, in order to solve a critical social issue.

No problemo till here.

My team was conformed by two girls and me. Let’s call them Ariana and Becka.

Becka & Ariana. Source: VectorStock

Becka was a freshment girl, and If I had to describe her in one word It would be: Excitement. She was always full of energy, Lots of ideas and she couldn’t wait to start working with us. During her first year of college, she had just a couple of programming courses, and her experience in programming was minimal.

On the other hand, we had Ariana. Ariana was a very relaxed girl, who lived in the same city where the enterprise was located. Besides all interns who had to move to that area, she kept living in her parent’s home, keeping her life outside work. She tended to left work on Fridays as soon as possible. Next day, in her stories, you could watch her in an awesome weekend adventure, even in another state. She didn’t looked interested in the project, she Continue reading "The Deadline Chapter 1 & 2"

Deadline: an interesting way of learning project management

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

Today, I'm here to write about a novel, but not any novel, "The Deadline: A Novel About Project Management." This novel has everything everyone can dream about: spies, corporations complots, and project management. The cover of the book This novel follows Mr. Tompkins (also known as Mr. T.), a recently fired manager trying to catch … Continue reading Deadline: an interesting way of learning project management

css.php