Managing self-organizing teams in an Agile Software Development practice is about encouraging and allowing developers to embody values of collaboration, creativity, quality, integrity, and individual initiative in an environment that provides sustainable pace and opportunities for personal development.

Hyperproductive? I don’t know but I’ll take it.

annotated burn up

I’ve written about how our agile practice, particularly continuous improvement, has re-organized our product and development group into one, high performing team. How this has resulted in less code, less waste, higher quality and more value. Jeff Sutherland talks about mature, agile teams achieving what he calls hyperproductivity. At this point, the team output accelerates and they outpace the organization around them. Performing beyond even our own expectations allows us slack to help our product team and our sponsors define … Read More

Continuous Process Improvement – Doing Less

I’m wary of the cliche’, “doing more with less.” When I started in my current role, my team consisted a development manager, a product manager, a business analyst, three developers, an outsource/offshore arrangement of 6-18 developers with its own full-time relationship manager and me, a non-individual contributor tech executive. We worked with a product team of three. We built our main US and six other variations over the course of 12-16 months – which was a great success in the … Read More

Agile software development and “value”

Scrum Release Burndown by kjudy

As advocates of agile software development we focus on practices. The hype on those practices is they produce software, “faster, cheaper, better.” And we sell our efforts with the promise of, “delivering value.” We speak of value as if the definition is shared, self-evident, contained within our backlogs and measured by our burn ups. At the same time we minimize the hard and long the struggle to achieve mastery, identify and address a material need, and sustain creativity and quality. … Read More

Agile NYC Presentation Handout

Here is a draft handout from my presentation at “Agile NYC”, Instilling Agile Values for Creativity, Self-Improvement and Organizational Change – A Manager’s Perspective.

Oops… learning lessons over and over

Here are agile software development mistakes that kick my ass whenever I let them: Know the assumptions in plans. Recognize when they change. Don’t abuse time boxing. It is a toe hold for over-committing. When the time box ends, the work ends. Doing Scrum means DOING SCRUM. Sloppy backlog. No Scrum. No Product Owner. No Scrum. No iteration boundaries and no commitment doesn’t make me “lean”.