The 10th annual state of agile survey is open through October 2, 2015. The survey explores the worldwide adoption of agile.
An interview about recent developments in requirement definition and management, how agile teams handle requirements and which problems they face in their daily work, using interactive diagrams and prototypes for conveying requirements, how interactive prototyping can be used with a lean startup approach, and what the future will bring us in requirements definition and management.
There is a positive correlation between diversity and financial performance and in an inclusive workplace, employees are more engaged which is crucial for retention and performance says Regina Chien. Having a diversity of thought and life experiences is going to help engineers create the best products.
Mike Orzen will talk about using core work systems to drive transformational behavior at the Lean IT Summit 2015. An interview on the benefits that organizations aim for with lean IT, why adopting and reinforcing new behaviors is essential to create sustained change, core work systems and work processes for IT organizations, and common missteps in lean IT transformations and how to prevent them.
Jørn Larsen, co-founder and CEO of Trifork, presented waste is a crime: don't waste your team at the GOTO Amsterdam 2015 conference. InfoQ interviewed Larsen about the "perfect world" to develop software products, aligning with many customers, why waste is a crime, why flow is important for software teams and what they can do to establish flow.
Olaf Lewitz gave a keynote about Integral Quality at the Agile Testing Day Netherlands 2015. InfoQ asked Lewitz about quality attributes, what causes poor quality software, the relationship between the structure and culture of the organization and software quality and about clarifying intent and increasing trust.
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.