Articles, Blog Posts, Books and Quotes on Agile Project Management
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.
Technical debt due to bad code quality is one the problem that every Scrum development team might face in their application. In this blog post, Henrik Kniberg discusses the causes of technical debt and provides some hints on how to manage it.
Velocity can be defined as a measurement of how much the Scrum team can get done in a Sprint, based on past results. In this article, Beth Macy discusses how reliable is velocity and how you can use it.
