Hans van Wezep, software architect at Philips Healthcare, talked about model-based migration at the Bits&Chips Software Engineering conference. InfoQ did an interview with van Wezep about the challenges in maintaining legacy software, why manual refactoring is error prone, using models to refactor and migrate a codebase, and the benefits of using models when maintaining legacy software.
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.
Calculating the business value of features is way beyond just a few numbers.
Computer-checked models can be used to prove that core communications and state management in a software program are 100% logically correct. Such models can also be used to generate 100% correct source code. The usage of formal methods can reduce costs and time to market and help to deliver highly reliable software products.
Vasco Duarte suggests that people should experiment with #NoEstimates to learn and find ways in which it can help them to deliver value on time and under budget. He is writing a book on #NoEstimates in which he explains why estimation does not work and how you can use #NoEstimates to manage projects.
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.
Making teams working together can be challenging, but it is often needed to develop and deliver large complex products. In her opening keynote about scaling dilemma's at the Agile Adria 2015 conference Mary Poppendieck presented ideas for organizations that want to scale agile.
InfoQ did an interview with Gil Zilberfeld about managing the expectations that organizations have of agile and how to prevent misconceptions, valuable ideas and practices from agile and what the future will bring for agile.
Technique of "value points" to determine the value delivered by any software project.
The product owner value game is a card game for teams. The objective of the game is to deliver as much value as possible. Teams learn to prioritize backlogs, plan iterations, and deliver results. The game helps teams to talk about agile principles, and exchange experiences.
Tester should go beyond their testing discipline and go into the organization. By asking questions they can start a movement that increases product quality and helps organizations to become more successful as Mike Sutton explained in his closing keynote at the Agile Testing Day Netherlands 2015 about test beyond quality – beyond software.
Dave Gray talked about how a connected company focuses on customer efficiency instead of company efficiency at the No Pants Festival 2015. A connected company has multidisciplinary teams where people work together to deliver a product or service. People working at a connected company feel empowered, they are able to solve problems together and to better serve the needs of their customers.
Introducing and managing change in organizations can be challenging. InfoQ interviewed Jason Little who is involved in organizing the Spark the Change Canada 2015 conference about the leadership and management approaches that radical companies use, on finding better ways to manage people and about what will happen to management in the near future.
This post covers the value of estimation in large and small scale projects and views on no estimation.
Joshua Arnold facilitated a workshop about Cost of Delay at the Lean Kanban France 2014 conference. InfoQ did an interview with Arnold in which he talks about the cost of delay: what it is, why it matters, the importance of quantifying it and some tips for getting started.