What Team Members Get Wrong with RetrospectivesVenkatesh Krishnamurthy explains some common misconceptions with retrospectives. Having a rigid mindset and believing that teams should only do retrospectives at the end of an iteration or raise issues only during standup meetings reduce agility and result in process-oriented thinking.
Meet These Preconditions Before You Think about Project EstimationsWhen estimating a project's release or budget, you can have only one number-one priority. If management has not thought about the constraints, they may be asking employees to cram in too many features with insufficient time. Read on for some conditions and guidelines about estimating for a project.
To Estimate or Not to Estimate—That Is the QuestionIn the agile community there is a movement called “no estimates”—where people are challenging the value and validity of estimating the work required to develop software. Scott Sehlhorst looks at the different perspectives of those who challenge estimation.
Estimation on an Agile Software ProjectEstimation is hard work, and people aren’t naturally good at estimation. But without an estimate, it’s hard to know how far off you’re likely to be. Estimates in the context of an agile project can help you better set expectations and improve stakeholder’s confidence in when you can deliver.
Busting Agile Prediction MythsWhen first hearing about agile processes, you might think that teams using an agile process cannot provide estimates, predictions, or commitments about what they will deliver. But, you can be agile and still manage risk and commit to a subset of what you predict.
