Standup is a straightforward scrum practice. But what happens to team dynamics when standup isn’t held at the beginning of the day?
The postcard is a quick way to inform clients of work completed in the sprint and a snapshot of value delivered by the team. Simplicity is key.
In many agile development projects, code will need to change frequently, and clean code that is easy to understand is easier to change.
Having a project glossary in your product development documentation will help build a baseline shared vocabulary for your project team and stakeholders.
It's easy to miss important technical details when refining agile user stories. Follow this checklist to make sure your team has the information they need!
Yes, you can plan more than a few weeks out on an agile project. Agile just gives you the flexibility to regularly rework the plan to meet your goals.
Breathe new life into your team's routine with design thinking activities for common Agile tasks: prioritizing work, assigning work, and retrospectives.
Don't pass up the little opportunities to build trust and credibility with your customers. It's never wasted time to engage them throughout a project.
Do your blockers explain what needs to happen next? Or who's responsible for it? Or when it's due? If you want them to get done reliably, they'd better.
Adopting an agile approach for software development? Here is a set of concrete pitfalls you can avoid as a leader in your organization.
On complex Agile projects, defining and refining user stories takes is a lot of work. The user story pipeline helps you visualize this process.
Estimating work is essential for planning for future work. But working through every nuance to provide an estimate can be too time-consuming.