Many organisations operate in highly regulated environments, such as healthcare, have concluded that in order to achieve the next level of product quality and safety improvements, not to mention enhanced competitiveness, adoption of a more Agile approach is required. In this presentation, you will learn how the Agile software development approach for high assurance systems addresses many of the challenges found in many highly regulated enterprise environments.
Agile and Scrum project teams can adopt many different structures. In her blog post, Elizabeth Harrin gives a good summary of five structures that could be used by Agile teams based on a presentation made by Catherine Powell at the Oredev conference.
You think retrospectives are the most boring meetings in Scrum and a waste of time? Or you are the ScrumMaster and you don’t know how to spice up your retrospectives? Unfortunately, I sat in a lot of boring retrospectives, too. But IMHO retrospectives are the meetings with the biggest potential for a lot of fun. I’ve some spices in my suitcase that will turn any retrospective into a remarkable experience. Join me, to learn how to facilitate a retrospective your team will love.
Technical debt a metaphor that refers to the eventual consequences of poor or evolving software architecture and software development within a codebase. The technical debt can be defined of as work that needs to be done to adapt a software to the best practices. In this blog post, Bastian Buch explains the step used in his organisation to reduce technical debt in an Agile way.
Whether people realise it or not, “freedom to choose” is the underlying principle behind many of the agile practices. We call this principle Real Options. An understanding of Real Options allows us to develop and refine new practices and take your business into directions it hasn’t gone before. Real Options also help us understand why some people resist some of the practices. Real Options is NOT about “deferring decisions to the last responsible moment”. It is a risk management approach to help improve decision making.
The main goal of a sprint review in Scrum is to receive feedback on the product that the team has built in the last sprint. How do you do when the product is created by many different teams and there multiple stakeholders who are involved in the Scrum project? In this article, Stephan Kraus explains how to scale the sprint review in Scrum using the fair concept.
Prevailing organizational structures are from the last century. Complete reorganization of traditional business and operation models is needed to support modern way of creating software. Agile transformation requires a holistic approach – makeover to something new is as much about culture, attitude and values as it is about structures. Active unlearning of old traits is needed in order to make room for the new. Straight talk, absolutely honest, frank and open conversation about both problems and successes, is a necessity of developing an agile culture. To have lasting and sustained results, understanding of underlying values and principles is essential. Role of change agents and other people supporting the transition is important in the cultural change. Fix-it-all methods and best practices won’t help as every person, team, and organization needs to find their own inspect-and-adapt path in the search for renewal. Conference slides: http://dl.dropbox.com/u/1404049/agilejkl/korhonen_tormala-beyond_scrum.pdf Video Producer: http://agilejkl.com/