Hakan Erdogmus and John Favaro explain why agility is good and when. They associate agility with flexibility which can lead to a better but more costly decision making process.
Richard Sheridan presents tools and techniques for creating an intentional culture of joy lacking fear and ambiguity, the most productive environment in his opinion.
Felipe Rubim discusses several forms of technical debt, emphasizing that every member of the team should consider it, and suggesting taking concrete steps in measuring and reducing it.
Leonardo Mattiazzi considers that Scrum and XP are not enough, and complementary Lean principles and practices are necessary to create an Agile culture across the entire enterprise in order to succeed
Anne Thomas Manes discusses SOA goals and objectives used to measure a system’s success, measuring the business value, SOA project metrics, and recommendations on proving the business value of SOA.
Eric Jan Malotaux discusses implementing SOA in small iterative steps, each step delivering value to stakeholders, using feedback from previous steps to adjust the requirements and design accordingly.
Manas and Clemens discuss deriving business agility from SOA and BPM, how SOA and BPM enable agility, and pitfalls/recommendations for organizational culture, business and technical architectures.
Russ Miles and Toby Hobson outline many factors to be considered when adopting a cloud solution, creating a wider view of the cloud from the development and business perspective.
We know solving DevOps problems improves your business operations but how do you do you explain that to your CEO or CFO? How do you get the executives to buy in and invest in DevOps solutions?
Next Generation of Business-Driven SOA: The Convergence of Performance-Driven Business and Service-Orientation
John DesJardins believes that the new SOA will measure their businesses alignment with IT in order to asses the impact of services or of changes or new initiatives, up-time, response time, etc.
Anne Thomas Manes talks about SOA's reincarnation. Old SOA had to die because it was focused on technology and products, while the new one will be focused on architecture, principles and practices.
Jake Sorofman talks on how to glue together the application development world and the business operations one in an automated, virtualized and cloud computing environment.