Deadline Driven Development

DDD or Deadline Driven Development, a term popularized in a well written article by Joshua Partogi (1) is real yet interesting problem to solve. It is not easy to tackle but nothing impossible right?
For me as software developer having enough experience of DDD is understatement, I’m fed up with it. No MVP, impossible deadline, no clear long term product and bussines vision, Long crunch time and everything in between. Don’t blame developers who think they’re a victim of vicious process.
Fortunately that article comes with good solution by prioritizing, slicing by the amount of cost of delay then doing continuous improvement afterwards. I will not try to explain that points, but I will add my own here.

The main point is to stop thinking as a bunch of victims and realize that we are also part of that vicious cycle. Get the position and speak up, present your concerns and ideas with clear reasoning and back it with good data. It is our job to be a good break for them, and giving options for each concerns.
Crying about how bussines or products people never understand engineer is useless, they will never fully understand us. Always improve team’s confidence for the next wave of impossibility in terms of technical efficiency and ability.

I said that full mutual understanding is not possible but at the end of the day we must agree that our goal is the same.

(1) https://medium.com/modern-management/deadline-driven-development-metodologi-software-development-terpopular-di-indonesia-1ea67ab0cfd0

Advertisements

2 thoughts on “Deadline Driven Development

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 )

Google+ photo

You are commenting using your Google+ 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 )

w

Connecting to %s