View articles related to: actuals adopting scrum Agile Agile Practices in Defect Fix Phase business Cargo Cult Agile case study certification Challenging coaching Coaching Assignments Construct the Sprint Backlog According to Individual Specialist Capacity CSC program CSC resources CSM CSP customer Daily standups Data Reporting and Metrics delivery devilish distributed teams Done environments estimation experience reports Five Scrum Short Stories Further reading Global Delivery Model How Effective is your Agile Team inertia Interactive knowledge legacy code management outsourcing planning probability product backlog product development product owner Project Management requirements retrospectives Scaling Scrum Scrum scrum and contracts Scrum Artifacts Scrum Ceremonies Scrum certification scrum coaching Scrum Gathering Scrum In A Nutshell Scrum in the Large scrum outside IT Scrum Roles scrum team ScrumBut ScrumMaster simulation Smarter Smartest software sprint backlog sprint planning sprint review sprint reviews sprints stakeholder management SVO-P test automation The Wisdom of Teams user stories velocity What do I do when...? what is scrum
Estimation with no historical data: a Monte Carlo approach
A Cure for Task Estimation Obsession: Just Don't Do It
The Case of the Time Tyrant: Don't Play Whodunit with Ideal Hours
Keep Your Team Seeing RED
Perfect Planning: Best Practices for Successful Sprint Planning
Language for Discussing Releases
"I'm taking off a letter grade because this wasn't turned in on the due date." "Don't be late!" Growing up, we quickly understand that being late is a bad thing. So when a project runs behind, we do whatever it takes to turn it around, even if those behaviors do more harm than good. Agile projects need a to discuss releases in a way that removes the guilt and focuses on appropriate action.
What's your sign? Find out what your burndown signature says about your team.
Scrum in a Fixed-Date Environment
|



