Articles, Blog Posts, Books and Quotes on Agile Project Management
When you observe a well-knit team in action, you’ll see a basic hygienic act of peer-coaching that is going on all the time. Team members sit down in pairs to transfer knowledge. When this happens, there is always one learner and one teacher. Their roles tend to switch back and forth over time with, perhaps, A coaching B about TCP/IP and then B coaching A about implementation of queues. When it works well, the participants are barely even aware of it. They may not even identify it as coaching; to them, it may just seem like work.
Adopting an Agile approach in a software development organization requires more than just sending some people to a Certified ScrumMaster (CSM) course. In this article, John Hill provides six recommendations for an enterprise Scrum transformation.
One of the major selling points of Scrum to developers is how much less documentation is involved. Developers worked hard to get where they are: a college degree, nights and weekends at home working through books and exercises trying to learn the latest language, and struggling through their first few projects to get something that works into production. They don’t want to come all that way just to spend most of their day in the word processor. They want to code.
This article discusses the challenges faced by technical projects like real-time networking applications that involve multiple Scrum teams.
In this article, Craig Larman and Ahmad Fahmy discuss how long does it take an organization to reorganize in order to adopt Scrum. This article is based on the transition done at Bank of America’s Merrill Lynch Global Securities Operations Technology where the software development teams went from a traditional activity based organisation (business analysts, developers, …) to Scrum.
There are as many assumptions and misconceptions about global development as there are about agile development. In this article, Jutta Eckstein tries to remove these misconceptions and explain how Agile can be implemented and provide benefits in distributed software development projects.
The Scrum approach recommends to deliver software incrementally in small iterations. This seems to be always an issue with activities that require a global view on the developed application like the software architecture or the user interface. In this blog post, Aviva Rosenstein, who manages user research for Salesforce, shares here experience about integrating user experience (UX) design into the Scrum development process.
