Voice levels were rising, as were the blood pressures in the room. Figurative lines were being drawn in the sand. The situation would really have been quite humorous if it hadn't been so intimidating.
In recent years, the "software craftsmanship" movement has articulated a sensibility long shared by senior developers entrusted to build high-functioning, complex systems.
Managing population health entails a complex set of activities involving many interconnected parts: health and its multiple determinants, healthcare delivery systems, information technology, and analytics.
The collection of development techniques and work management practices commonly referred to as agile methods has evolved rapidly over the past decade to the point where it is difficult to find any sizable IT organization that doesn't make claim to some sort of agile initiative.
As a method for practicing continuous improvement on a day-to-day basis, the improvement kata complements Agile methods and integrates with familiar Lean tools.
The authors conclude this issue of Amplify by analyzing systems for governing greenhouse gas (GHG) emissions in markets in the US. They argue that public-private partnerships (PPPs) have the potential to fill the void in market governance left by the failure of the government to enact comprehensive climate change legislation. The authors highlight the Science Based Targets initiative (SBTi) as a tool that provides companies and other organizations with the means to make specific, credible plans to achieve decarbonization. They argue that aligning PPPs with SBTi target setting would be an effective mechanism to accelerate carbon emissions reductions.
It is clear to most people by now that no one methodology will fit every software project. What is not clear is where to go next. If concrete advice can't be given across projects, how are we to find meaningful methodological advice for our projects?