Articles, Blog Posts, Books and Quotes on Agile Project Management
“Perhaps you’ve read a book, on Extreme Programming and have decided that is the right approach for your company. Or maybe you attended a Certified ScrumMaster training course and think Scrum sounds good. Or maybe you read a book on a different agile process, and it sounds perfect for your organization. In all likelihood, you’re wrong. None of these processes as described by their originators is perfect for your organization. Any may be a good starting point, but you will need to tailor the process to more precisely fit the unique circumstances of your organization, individuals, and industry.” Reference: “Succeeding With Agile”, Mike Cohn, Addison-Wesley, 463 pages, IBSN 978-0-321-57936-3
The article “Bridging Agile and Traditional Development Methods: A Project Management Perspective” by Paul E. McMahon discuss agile project management adoption. This article identifies specific project management conflicts that companies face based on actual project experience, along with strategies employed to resolve these conflicts and reduce related risks. This article will help you understand the risks, issues, and strategies that can help your project and organization succeed.
“After working for some years in the domains of large, multisite, and offshore development, we have distilled our experience and advice down to the following: Don’t’ do it.” “Scaling Lean & Agile Development – Thinking and Organizational Tools for Large-Scale Scrum”, Craig Larman & Bas Vodde, Addison -Wesley
The article “Agile, Multidisciplinary Teamwork” by Gautam Ghosh presents techniques and tools used to create requirements with a team composed of the different participants of agile projects.
“Excuses Might Be the Response, Not Necessarily Resistance” is an interesting blog post on how people are unable to change the way they work.
“Estimating With Use Case Points” describes the process to measure the size of an application modeled with UML, using use case points.
“Self-organizing teams are at the core of the agile management, but the concepts have become corrupted – and counterproductive – in parts of the agile community. Although self-organizing is a good term, it has, unfortunately, contingent within the agile community who encourage an anarchistic management style and have latched onto the term self-organizing because it sounds better than anarchy. As larger and larger organizations are implementing agile methods and practices, the core of what it means to be agile – an empowering organizational culture – may be lost because large organizations will reject the cultural piece of agile.” Reference: “Agile Project Management”, Jim Highsmith, Addison-Wesley, Second Edition
