This article examines something called “The Daily Scrum Meeting” used by Scrum Teams on Agile Software Development Projects around the world. Using some real-life stories and cartoons, you should walk away from this with a better understanding of what not to do, what to do, and then how you can make changes if the first team looks more like what your Scrum Team is doing today.
Continuous feedback is part of basic principles of Agile project management, using techniques such as Test Driven Development (TDD), Continuous integration or daily stand-ups meetings that allow the Scrum team to share concerns about potential challenges as well as coordinate efforts to resolve difficult and/or time-consuming issues.
Scrum is often mentioned as an approach that minimize project documentation to only what is really useful. However, other persons can need written content to work with the developed software. This blog post discusses the role of technical writers in Scrum projects and how agile principles should apply to their activity.
Your team has adopted the relative story point estimation and you are now ready to jump into your first planning poker session. Where do you start? What is a 1-point story? What is a 3-point story? What is a 13-point story? Your team is looking to you and this process is almost as new to you as it is to them.
In this short video, a development manager explains how they use Scrum for development work in the sprints, but use KanBan to deal with issues with released software in the field. Their helpdesk prioritises the issues and the team uses the KanBan board to solve these issues as fast as possible.
Marc Löffler shares in this blog post 11 hints to improve all the Scrum meetings. He discusses daily stand-up meeting where he suggests to show colleagues what your currently working on instead of just talking about it. He also make proposals to improve the sprint planning, sprint reviews and retrospectives.
In this podcast, Mario Cardinal explains his ideas around agile architectures and how to trace system architecture back into requirements.