
Cost of delay and opportunity cost when you don’t build quality in
Let’s talk about cost of delay – the cost of having NOT done something. Basically the opportunity cost of choosing to do one thing over another. Seems simple enough but it’s not.
Let’s talk about cost of delay – the cost of having NOT done something. Basically the opportunity cost of choosing to do one thing over another. Seems simple enough but it’s not.
Busy. I’m busy. I’m too busy. I don’t have time to think – hell, I barely have time to sleep. Between work commitments, friend commitments, relationship commitments, and building my own brand, I am left with little time for myself. I’ve gotten into a pattern of trying to make every second add value (work-type value). What does it turn into? Burn out and ineffectiveness, and that is not what anyone wants or needs.
Want loyalty? Hire FTEs! Want an expendable workforce? Hire contractors! Want short term experts to solve problems? Hire consultants (*at a premium price)! But what if you want high performing Agile teams? What type of workers should you look to hire then?
Introversion versus extroversion has been a hot topic over the past few years, especially since the release of Quiet by Susan Cain. In IT it is no different. Everyone knows the stereotype of the “typical developer” – the one who only wants to sit in their cube and code by him or herself all day. But it’s just that, a stereotype, based on some facts but not true for all. So how are we more inclusive of that person in Agile where collaboration, co-location, and teamwork are valued over solitude? Secondly, how do we encourage introverts to be leaders which is historically and stereotypical a role for extroverts?