There are now several frameworks designed for scaling agile. This talk explains the flaws in such frameworks, why they so often fail to produce the desired effects, and what we should do instead. It also addresses some common organizational obstacles to moving fast at scale: governance, budgeting, and the project paradigm – and discusses how to address them. Warning: this talk includes liberal use of real, statistically sound data.
Customer value. Everyone wants to deliver it. Everyone “believes” that they are delivering it. But are you? How do you know? This provocative talk challenges the audience to see their work in a different way and consider adopting value stream management as a means to become a more nimble organization that delivers even greater customer value.
XP Conference India is a conference taking place in India that focuses on all the technical practices of Agile software development like clean code, refactoring, code smells, continuous delivery, Test-Driven Development (TDD) and Behavior-Driven Development (BDD).
The Agile Manifesto says that “The most efficient and effective method of conveying information to and within a development team is face-to-face conversation”, but many meetings are a dull waste of time, even for Scrum teams.
Velocity is one of the most common metrics used – and one of the most commonly misused – on Scrum and Agile projects. Velocity is simply a measurement of speed in a given direction, the rate at which a team is delivering toward a product release. As with a vehicle en route to a particular destination, increasing the speed may appear to ensure a timely arrival.
Sprint retrospectives are an important tool for Agile software development teams that want to implement continuous improvement and adjustment to their working context. In this article, Jesus Mendez provides some techniques that could help improving the outcome of your Sprint retrospectives.
Allan Kelly outlines the #NoProjects agenda and discusses the role of teams as the unit of production and the team life cycle. Good projects make for bad software. Software which is useful is used and demands change, stop changing it and you kill it. In a world without projects how do you manage work? The answer is teams. Teams are the means of production, work should be based around teams and teams should be stable.
Scrum Expert Copyright © 2009-2024 Martinig & Associates