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.
In my experience, there are three critical elements that need to be present in ‘interlocking proportions’ for any organization to truly achieve a sustainable long-term success. When I say ‘interlocking proportions’ I am implying two key things – one that there must be a natural and mutually complementary fit among all the components, and secondly these components are in such measure that they complement, ideally amplify, each other, rather than canceling out one component at the cost of other component.
India is a new gold rush market. Home to some 1.2 Billion people, half of whom under the age 25, and buoyed by the recent economic growth, the country is poised to be a major economic powerhouse for the next few decades before becoming the second largest economy by 2050. In this short article, let’s review some of the data and trends that I discussed earlier in my presentation at the PDMA conference in Orlando, Florida.
Pune is hosting India’s first Scrum Gathering this year in July with the theme of “Scrum – Kal, Aaj aur Kal”, meaning the past, present and future of Scrum. I appreciate all efforts by Madhur Khaturia and his team in making it happen. I hope and believe it will be yet another milestone in India’s journey towards agility, and will stimulate a whole lot of new ideas and conversations thus ultimately leading to increased awareness, higher adoption and more breakthrough products from India.
Problem-solving in the past has been dominated by methods involving rigorous and meticulous planning and flawless execution – something that has been questioned, largely by results (or rather the absence of it) in the recent years, if that is (still) the best approach when there are so many moving parts and the external world changes in a blink. We frequently ‘blame’ old practices of assembly plant-style waterfall days where it took years to get a project team to jump multiple hoops and just get a project done – in most cases, hopelessly delayed, unacceptable quality and overbudget.
In continuation of my earlier blog post on ‘Does Agile Kill Innovation?’, I had a great time moderating the panel discussion at Agile India 2013 with Henrik Kniberg, Owen Rogers, Sujatha Balakrishnan, Udayan Banerjee, Praful Pillay and Sudipta Lahiri. The panel discussion was literally the last program at the end of two long days of management conference – but despite that, we had 60-70 folks throughout the session.
Distributed and virtual teams are a reality of today’s world. It is not just limited to well-heeled MNCs – we see countless everyday examples of such teams with NGOs, startups, voluntary efforts, college project and so on. There is more to working with people from different time zones and cultural contexts than we realize. Problem is, most of us haven’t been exposed to, or adequately trained to handle such diverse teams – not just as a manager but even as a team member.
I will be moderating a panel discussion on this topic at the Agile India 2013. Given the incessant pace of technology evolution, ever-growing competition where product functionality is hardly the differentiator anymore (if it ever was!), shrinking time-to-market expectations where ‘continuous deployment‘ seems to have been relegated to a hygiene …more
In recent times, performance appraisal has been a subject of intense ideological debates. Performance appraisals have traditionally served as a mechanism to basically assess an individual’s performance in the previous year to reward employees in terms of compensation and career progression in the coming year. On one hand, organizations, at least the reasonably larger ones, need some systematic and transparent way to deal with employee’s performance evaluation. On the other hand, with more part-time and virtual employees entering the workforce on a very mission-based engagement as opposed to building a long-term career, the whole idea of formal performance management systems seems to be rather backdated. So, what’s the real deal?
What is the first thing that comes to mind when we see the problem? Most of us immediately jump in to start solving it. While this might appear to be a natural instinct and a logical choice for some simple problems, reality could often be otherwise, especially for complex problems. If we don’t know enough about genesis of that problem, we might spend countless hours fixing it, and yet hardly make any meaningful headway. Or, we might fix it in the short-term, but might not solve it in the long-run, i.e. address the root-cause behind it. For all we know, the first thing we do might actually be the worst!