The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Pollyanna Pixton is well known in the Agile community, especially for her work on leadership. In this interview with Deborah Hartmann at Agile 2008, she discusses what must be present for successful Agile adoption. In response to a question about what parts of the environment must be present for a culture of trust Pollyanna says:
Safety is always a big one. Being able to count on what people say, when people say "I will do this" you know they will do it. And that is very important. It has to eliminate fear, you have to eliminate as much as debilitating fear as possible so sometimes I find in organizations that some leaders are indiscriminate about how they manage conflict in the teams or they manage the behavior, if you want to call it managing behavior however you may look at that but they may see people and think they are not productive and they will reprimand them and it will be indiscriminant and that creates fear and it takes a while to work with a team, usually takes about a day before they will finally start talking about the fear and what it is, you have to build up the trust in the seminar, until they finally tell you and it is always instant like it is a switch, as soon as they say it, it happens and one organization I worked in somebody had abused the Internet, so everybody was not allowed to work on the Internet.
This interview is full of sage advice to Agile leaders, such as this answer to the question "what advice would you leave with project leaders right now?":
Well, I think that the advice is not just for project leaders but I will talk about that. It's about project leaders, middle management leaders and executives including it. It's like the book that we are writing called "Stand back and deliver". You have to let your teams to become creative and innovative. You have to let them do their work and choose their work and decide how to do it. So you essentially have to stop micro managing. So you don't get to tell people what to do anymore. You help them stay focused by asking questions.
This is an informative and enjoyable interview on an important topic today.
Case Study: IBM's Agile Transformation
18 agile and lean practices for effective software development governance
Five Key Practices to Agile ALM
SCM best practices for multiple processes, releases & distributed teams
In today’s hyper-competitive world, later may be too late to adopt Agile development and this Roadmap for Success will help you get started. Download "Agile Development: A Manager's Roadmap for Success" now!
Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.
One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.
InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.
Alex Papadimoulis discusses ugly code, where it comes from, how to avoid it, and how to get rid of it.
John Davies examines Visa’s architecture and shows how enterprises have architected complex integrations incorporating Hadoop, memcached, Ruby on Rails, and others to deliver innovative solutions.
Sean Comerford unveils ESPN.com’s architecture, what components are used and why, and the current changes the website goes through.
Are there repeated patterns of failure on Enterprise Agile Enablement efforts? Sanjiv and Arlen discuss Seven Deadly Sins to avoid when adopting Agile in an enterprise.
Erik Dörnenburg answers: What is Enterprise and Evolutionary Architecture?, discussing 4 issues: Turning strategy into execution, Ensuring conformance, Where do the architects sit? Buying or building?
No comments
Watch Thread Reply