Coding Intent

Navigation

Search

Blogroll

Disclaimer
The opinions expressed herein are my own personal opinions and do not represent my employer's view in any way.

| |

E-mail

Total Posts: 9
This Year: 0
This Month: 0
This Week: 0
Comments: 1

Monday, May 04, 2009

Decisions in isolation

Monday, May 04, 2009 10:30:38 PM (Cen. Australia Standard Time, UTC+09:30) ( Agile )

Decisions made in isolation are often wrong. I’ve been told on occasion that I don’t give enough information and that I’m too optimistic. Both are a fair call and I’ve tried to address those in what I do. It’s good to have feed back because changes cannot be made in an insular environment.

The same rules apply when trying to effect change in a team environment. A team needs to be able to look at the practices and process that are being used and be able to critique them, it’s a vital skill to learn. When decisions are made without input from the team and then forced on them its bound to fail. I realize that not all decisions can be voted on and that someone has to make the decision but that decision needs to be made with all the information.

When making decision make sure that you have ALL the information that you can get.

Comments [0] | Trackback |

program intently and expressively - The PIE principle

Navigation

Search

Categories

On this page

Archive

Blogroll