Tracking change and innovation in the enterprise software development community
Free Book Offer
SOA Demystified
$40 Value
QCon London 2010!
March 10-12, 100
Speakers, 80 sessions,
"THE" team leads and,
architects conference.
Scaling Scrum
in the enterprise?
ScrumWorks Pro
can help.
Start a trial today
Recorded at:
Presented by Mike Cohn on Aug 07, 2008
Learning to be a Good Product Owner: Foundation Skills
Technical Debt and Design Death
hao ka
This is an excellent diagnosis of the symptoms and problems encountered in an Enterprise Agile Adoption scenario, with a practical analysis of its prognosis, possible treatment plans and ideas for monitoring and maintaining the continuous improvements in it.
Thanks for sharing your experiences and ideas.
Kripanidhi
www.scrumtales.blogspot.com
www.binaryessentials.com
Mike's point about you shouldn't try to get a team to be self-organising by command and control is one of those insightful moments that everyone should pause and think about.
In the past during interviews, discussions etc. I've mentioned taking a light touch approach as discussed in Sanjiv Augustine's "Managing Agile Projects" book and so many people, including some who have been seasoned agile proponents, have mentally taken the opposite angle of "the team won't become self-organising unless I tell them how to be", and dismissed the light touch approach.
IMHO to get a team to move towards becoming self-organising needs continous encouragement, respect, shared knowledge between all team members, and most of all, knowing when (as a manager, coach, or mentor) your pre-conceived mental image of them being self-organising day to day should be retired as they've reached their own disciplined state of being self-organising and have moved from the norming to performing stage of team development.
Brian Marick takes us through a quick tour of the most important values and challenges to adopting Agile successfully (they aren't the typical challenges and values we hear in the community).
The line between development and architecture is tricky. Does it exist at all? Is an ivory tower actually needed? There's a balance in the middle, but how do you move from developer to architect?
The word 'authority' sometimes produces an allergic response in hard-line agilists. Freedom and authority – both are bad if misused and both are good if used in right spirit for a noble cause.
"Getting Started with Grails" brings you up to speed on this modern web framework. Companies as varied as LinkedIn, Wired, and Taco Bell are all using Grails. Are you ready to get started as well?
Those familiar with only ITIL V2 often scoff at the thought that ITIL could serve as a governance framework for SOA. With ITIL V3, the focus of the framework shifted towards service-orientation.
SpringSource CTO Adrian Colyer discusses AspectJ, SpringSource's dm Server and tc Server products, OSGi and Scrum.
Heroku's Adam Wiggins talks about Rails, Background Jobs, Add-Ons, Ruby, and how Heroku manages to work around Ruby's inefficiencies using Erlang and other languages.
For Grady Booch the foundation of a good architecture is patterns, SOA being just one of many patterns. In this Second Life presentation, Booch attempts to bring more clarity on what architecture is.
3 comments
Watch Thread Reply