Pain of making schedules.

.

Making a schedule for the software project is a painful activity. It is amplified more if you do not know what you are doing. Software schedule can be at most an estimation in the early phase of the project. The real schedule details will be available only once the project is underway and things become more clear.

I believe that the developers are one who can contribute to a meaningful schedule, the managers the least. The manager do not have enough information to arrive at the schedule estimate, but most of the time, they tend to push the deadline on the developer. The developers who do not stand up this, tend to agree to the bad schedule and end up screwing their life and work.

There fore developers should vote against a idiotic schedule when they encounter one. They should give or help to make a meaningful schedule. The lead and developers should meet more often to see if they are on track. If not they should take corrective action to get the project schedule on track.

Developers should only consume what take what they can chew, if the deadline is fixed drop the features, if features are fixed then extend the deadline. It is impossible to have maximum features in a very limited time span.

.

Advertisements

5 Responses to “Pain of making schedules.”


  1. 1 Jesse Grillo Jesse Grillo September 2, 2017 at 1:33 am

    awesome post! I could not resist commenting. amazing work, keep it up. Your post really maked me think.

  2. 2 investor adviser August 31, 2017 at 6:08 pm

    I was reading on Friday when I heard about your website. Your blog is really useful to me. Spot on with this. magnificent website.

  3. 3 software September 29, 2014 at 2:03 am

    What a information of un-ambiguity and preserveness of valuable familiarity regarding unexpected emotions.

  4. 4 Karthi April 23, 2007 at 1:32 pm

    Venkat, Wish if it was due to semicolon! There is more to it like null pointer access. sob…

  5. 5 Venkat April 22, 2007 at 7:54 am

    No doubt you wrote this whilst sitting in front of thousands of lines of code and finding out that the HUGE amount of errors you were getting was due to not putting a semicolon after a statement?


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




Pages

Thru Lens

Tweets

View Karthikeyan S's profile on LinkedIn
Alltop, confirmation that we kick ass

%d bloggers like this: