How (and Why) You Should Split User StoriesThe Scrum process is built around the process of implementing user stories. Many teams struggle with the challenge of knowing how to split user stories so that the individual stories have atomic value and are properly sized.
The Testing Lean Coffee ExperimentThe Lean Coffee process is a great way for a diverse group of people to discuss topics that are meaningful and relevant to all participants. Lisa Crispin writes about her experience experimenting with a testing version of the Lean Coffee™ format.
Using Agile to Avoid Excessive MultitaskingBy keeping priorities clear and avoiding excessive multitasking, you can provide teams the space to work with attention to quality and adaptability. Agile processes give teams more control over their time, and this control can lead to the teams' being happier and more productive.
Counterintuitive Tips for Agile Collaboration While true for all teams, agile software development is especially reliant on teams and collaboration. What makes a team function well can be counterintuitive.
The Differences between a Project Manager and a ScrumMasterIn the traditional model of software development, the project manager is responsible for project planning, estimating costs, and other tasks. However, with the popularity of Scrum and the role of the ScrumMaster, the project manager's responsibilities, although diluted, are not going away.
Agile vs. Waterfall DevelopmentWhile there are many similarities between agile and waterfall development methodologies, we have to face the truth that agile was created because of the real and perceived failures of the waterfall methodology in software development.
Tips for Starting (and Ending) a Process AnalysisWithout boundaries, a process analysis could go on forever. Adapting things learned from working in agile software development, Scott Sehlhorst provides tips for starting—and ending—a process analysis.
How Automation Benefits Agile Technical PracticesAutomation is an important aspect of agile technical practices. Automated builds, testing, and deployment enable developers to implement features and refactor to improve code quality with confidence. So, is there any reason to be skeptical about the benefits of automation?
