Fred George talked about the Challenges in Implementing MicroServices and The Secret Assumption of Agile at the GOTO Amsterdam 2015 conference. InfoQ interviewed him about how make microservices as small as possible, challenges when implementing microservices and how to deal with them, why programming style matters, and what developers can do to develop their code writing skills.
The discussion on ITIL vs. DevOps is a common one. There are different views: ITIL and DevOps have different mindsets; ITIL and DevOps are compatible; they are different but both have their place in the IT department. Charles Betz, member of the Open Group IT4IT Forum, argues that their principles are at odds. ITIL is trapped in a phased workflow mindset. DevOps embraces lean product management.
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 did an interview with Menno Vis, IT director of bol.com, about the benefits of increasing agility, how bol.com deploys Scrum, using roadmaps with agile, the challenges that have been faced when scaling agile, the main focus area's at bol.com for agile scaling, establishing loosely coupled teams, and the things that bol.com does for their people to have fun while doing their work.
InfoQ interviewed Andrea Provaglio about business models for execution, optimization and discovery, dealing with uncertainty and leveraging it to create business value, understanding both value and cost, growing a discovery mindset, and creating a culture where people have the courage to make mistakes and can learn from them.
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.