At the GOTO Amsterdam 2015 conference Mary Shaw talked about progress towards an engineering discipline of software. She explored what it means to have an engineering discipline, how far we have progressed toward having one for software, and what can be the next steps.
An interview with Rob Howe, host of the MDSE session at the software engineering conference and CEO of Verum, about the state of practice and recent developments in model driven software engineering, the usage of this technology, whether he considers model driven software engineering to be a proven mature technology, and what the future will bring us in model driven software engineering.
InfoQ interviewed Frank Penning, PMO manager from Philips Lighting, about the main challenges that Philips Lighting is facing in product development, why Scrum is not enough, how they apply SAFe, and the benefits that they have gained from deploying agile methods for product development.
Martin Fowler describes yagni practice, why its is important and the costs of building presumptive features. Yagni is an acronym that stands for "You Aren't Gonna Need It". It is an Extreme Programming (XP) practice which states a programmer should not add functionality until deemed necessary.
Total Cost of Ownership (TCO) can be used for investment decisions and financial benefit analysis. When applied to software it covers the initial development costs and subsequent maintenance costs until phase out of a product. TCO can support architectural decisions and management of technical debt.
InfoQ interviewed Hans Aerts, vice president software development and agile coach at TomTom, about why they decided to adopt SAFe and how it was introduced and used to simplify the organizational structure and stop doing projects, why they focus on throughput rather than output, how they modified SAFe for Custom Systems, and what using SAFe has brought TomTom.
You can increase the quality of products by constantly increasing the level of automation of the delivery process and working with DevOps teams who constantly deliver small features to get quick customer feedback. A case story from ING Lease explaining the problems they had, experiences from the first steps of their agile and DevOps journey and exploring what they want to achieve in the future.
This post talks about the strategies to manage dependencies between product backlog items.
Less functionality can make a better product according to the “Worse is Better” concept described 25 years ago by Richard P. Gabriel. According to Kevlin Henney and Frank Buschmann we can learn from the worse is better concept for development and architecture with agile and lean.
Hackathons are events where developers work together during a fixed period to collaboratively develop software. They provide learning opportunities and space for developers and organizations sponsoring the hackathons to network and have some fun.
Scott Sehlhorst, product management and strategy consultant describes two views of the product roadmap.
The real requirements of a product are not the functions that are needed, or user stories that have to be delivered. It is the possible improvement of performance that customers can get from using the product said Matteo Vaccari. At the XP Days Benelux 2014 conference he facilitated a workshop together with Antonio Carpentieri about defining the value that is needed by customers.
Scrum of scrums can be used to scale the daily stand-up meeting when multiple teams are involved. Its purpose is to support agile teams in collaborating and coordinating their work with other teams. Several authors have shared views on scrum of scrums, with experiences of using them.
Experimentation using for instance lean startup can help you learn about your customers and find out which features and product would be valuable. The value however comes from building products and actually delivering them to customers. You need to find ways to balance between experimentation and delivery.
Would better user stories improve software delivery? Gojko Adzic thinks applying small changes to the way teams manage their user stories can have a huge impact on the actual outcomes of their software delivery. He announced that he wants to write a book about improving user stories if at least 5000 people show that they are interested by pre-registering themselves in January.