h1

Getting Real – Chapter 3

September 16, 2008

It is almost midnight and I haven’t posted this blog entry.

It was a 5-hour delay blog post due to some technical reasons. Sorry for that.

Now I wonder, why does my entry doesn’t show up?

Yeah. I posted it in a page not in a blog entry. Stupid thinking.

Sorry Sir David for the delay. Hope you still read this one.

Anyways, I here to talk about something what I’ve learned in the past readings.

After reading the Chapter 3 of Getting Real, I was able to grasp the idea of knowing how to construct an appropriate software features which allows user to use them efficiently and effectively. Building a software is a commitment, you should learn to adapt on what is required and what is only needed by people.

The tendency of having a large scope in building a software, you will never be finish on time. Plus, it would definitely cost you a lot. Remember the triple constraints – Scope, Time and Cost. Without proper management, any project would eventually become a failure. I almost forgot. We should also add Quality as part of the criteria.

In a changing environment, stakeholders become more demanding. It would be an advantage, specially for programmers to lessen their features, or should I say, start with a minimal feature. So that if there would come a time that the software really need that expansion or the development, developers or programmers could able to adjust depending on the demands of their clienteles.

Keep it short and simple. K-I-S-S. It was always been in my head for a very long time. However, I still tend to violate this simple rule. I do things way out of the scope. I have to admit, I’m not really good in pointing out good scope – I usually do things that are outside the boundaries.

In Getting real, they wanted things to be K-I-S-S.

Less mass also applies on having a small team. Based on what I had read, it is better to start in a small team because you can communicate well about the project. Also, the team members will be forced to work hard on the project to finish and deliver it on time. A small team can only be effective and efficient if the team members are competent enough to do the job.

The author emphasize on how less mass, or less feature, applies on smaller teams. It is a good start for people to build a small group rather than focusing on building larger ones. Just like in reality, smaller groups would let each members do their share. No slack offs. No worries. And because everybody do their share, a project will be accomplished on time. And the good thing about smaller groups – that is, quality. Because of minimal number of team mates, should I say, they are ‘force’ to do things, thus, squeezing out their brain cells to think more – to do things more.

In every project we do, we must learn to determine what are the constraints or hindrances along the project. It is important that we must learn to react things before a risk or problem would probably happen. Always remember the Murphy’s Law. Anything can happen – and it would even become your worst-case scenario.

One thing the article pointed is what is the difference between smaller companies to bigger companies. The advantage for small companies – less features. The good thing about less features of an application is that they can able to response to their clients quickly. Once they deliver it to them, the clients are satisfied – so are they. But the thing is. Nothing can be fixed forever – we need to adapt what really the world need. We soon improve our products, our services. And because markets are conversations, we were influenced by different factors – political, historical, social, and others. This innovation would eventually grow if communication between two people will be existing. Communication is good way people could share ideas and information to develop and to improve the way of life.

Thanks for reading. Comments and suggestions are welcome.

God bless.

Good night.

Advertisements

One comment

  1. Alright, I read it 🙂



Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: