If the only reason you ‘think’ is so that you could think along what others are thinking, you might as well not think at all! Life is too precious to be lived in ‘more of same’ format.
Suppose you are the new program manager assigned to a program. How would you go about finding your way inside the complex maze of a program, its stakeholders, sponsors, component teams and various vendors?
Burnout is a serious issue for several countries, industries and people, even if we don’t acknowledge in as many words. In our industry, where heroism, cowboy programming and all-nighters are considered cool and an integral part of the software subculture, there has been a (really) small effort to address work-life balance.
Why are we so parochial in software industry about not recognizing the bigger economic sense rather than limiting ourselves to a singular idea that collocated teams are the best option?
Feedback is perhaps the most important aspect of the overall agile lifecycle – without a proper, honest and timely feedback, there is no ‘adapt’ step in the inspect-adapt cycle. However designing a proper feedback instrument for a human-human interaction, like a training program, is a totally different thing because it entails imprecise measurements that are often influenced by people’s mental models, skills and experiences, and not to mention – their calendars! Needless to say, these feedbacks could mean anything to different people on different days.
Even the ideas need to procreate in order to produce better ideas! Innovation tells which ideas should procreate, and Design tells how they should procreate! They both must be present in a ‘cooptetive’ manner – competing and yet collaborating at the same time.
Startups that operate under a stealth mode achieve over 90% failure rates. While they might have bright ideas, access to top talent, adequate funding, etc., they typically fail to accomplish their original objectives. A key reason behind such spectacular failure rates is premature scaling at each stage of the startup. In this talk, we will examine the mistakes that startups make, and what we can learn from the Customer Development model proposed by Steve Blank to improve better chances of survival and growth.
I still continue to be amazed (thought ‘shocked’ and ‘dumbfounded’ will be a more appropriate words here) by the amount of dogma in agile circles. Do this! Don’t do this! Wasn’t agile meant to liberate us from the tyrannies of the so-called big monolithic non-agile white elephant processes, and create a more nimble mindset, flexible culture and adaptive process framework where ‘inspect and adapt’ was valued more than ‘dogma and prescription’?
This blog post is about those brave 5% who decide to take matters in their hands and leave the comforts of corporate job and social prestige to walk alone into an uncertain but perhaps more exciting future. I salute their fortitude. Unfortunately, in many of those cases, they are extremely ill-prepared for the uncertain future that lies ahead…the internet doesn’t know them!
Plans have a huge credibility problem. For large part of recorded history, they have always had this problem. With all the advancements we have made in estimations, forecasting, scheduling, risk management and planning, our execution still continues to challenge us, at times even confound us.
User stories are meant to be a placeholder to initiate an early conversation between the product owner and the team on key hypotheses so that a quick validation of them could be done to refine/confirm/reject our understanding of what the customer really wants.