A case study on creating buy-in and commitment for flow thinking using a mental model and metaphor was presented at the Lean Kanban Central Europe conference. InfoQ interviewed Håkan Forss and Erik Schön about their journey from methods & tools to principles & mindset and how they use visual management to implement flow thinking and improve the product development flow at Ericsson.
Coming to decisions about which products to build or which features to add to existing products can be difficult. The lean startup approach can help to get insight into the needs of customers, and to build a sustainable business around a set of products and services that serves those needs. How can enterprises adopt the lean startup approach to become more innovative and competitive?
To stay competitive, enterprises look for ways to do innovation inside their organization. A first step can be to make time available which people can use to think about new products and services and discuss ideas and develop concepts, for instance with a dedicated “full-time” innovation team, by arranging frequent innovation time-slots, or by organizing short and intense innovation workshops.
There are different types of pivots possible in lean startup, which help you to decide whether to persevere or pivot during product development. They each with their own purpose and ways to use them. Let’s explore some of them to see when and how you can pivot? Or maybe have to decide that it’s better to quit?
The lean startup is about fast delivery of desired products to customers, and increasing your understanding about the needs of customers. With the lean startup, people can learn faster from failures and become better innovators. There are teachers that use a lean startup based approach in education, which helps their students to learn faster.
Thoughtworks recently published a whitepaper including a maturity model for continuous delivery (or CD) as a response to research indicating that most companies understand the importance of innovation, but are not able to deliver software quickly enough to meet the needs of business leaders.
Governance has reared its head up again, this time in the API community and questions have been raised about its relevance especially in organizations where innovation is the focus. This was a hot topic at the recent API Strategy and Practice conference and the debate continued in the blogosphere.
Swarming is a technique that helps agile teams to deliver working software fast and frequently. What is swarming, what are the benefits of swarming, and when and how to apply it?
Innovation Games celebrates their 10 year anniversary with a Summit in Santa Clara California. The Summit features Alexander Osterwalder as the keynote speaker.
After seven years, over 500 innovation projects and high profile endorsements from Dan Pink and other leading publications that resulted in hundreds of organisations copying the concept, Australian software company Atlassian has had to rename its famous innovation day concept.
This is a survey of the most important software development trends for 2012, as voted by the attendees of QCon London 2012. It includes technologies like Big Data, HTML5, Mobile, NoSQL, Continuous Integration, GPUs & Multicore, Cloud - PaaS, Cloud - SaaS, Cloud - IaaS, Asynchronous Technologies, Lean, Scrum, Google Dart.
Tony Wong, a project management blackbelt, enumerates some practical points on individual procutivity. This article wonders how well these apply to software development and contrasts his list with that of other lists.
Enterprise Architects may be disproportionally concerned with portfolio consolidation, standardization and simplification instead of offering leadership in business technology innovation. This is the proposition offered by Forrester analyst Brian Hopkins in a recent blog post.
Technology is recently associated with unrest in the media but an Innovation Games event in San Jose shows how Governments can use Agile technology to collaborate with the "people".
Building software is closely associated with managing a lot of constraints. These constraints might be in terms of time, money, technology, decisions, compatibility, regulatory, people, process or all of the above. Jim Bird discussed the constraints imposed by Scrum, XP and how they help in fostering creativity and building the right software.