Slack is an agile practice--and in planning for successful sprints that yield consistent, high-quality results, it is essential.
234 items found
In a software development project, estimates are important to help us predict how much time will be necessary in order to finish a set of activities, or to select and prioritize scope for a release or iteration.
Follow discussions in any online PM community over a couple of weeks and you'll run across at least one discussion thread vilifying agile project management. But at least one practitioner is not quite ready to throw the baby out with the bath water...
How can Scrum in particular be best applied to game development?
Confused by the fuzzy way that agile teams and projects are managed (or manage themselves)? Frustrated and disappointed by the negative attitude toward managers and management in general? You're not alone...
Most of us working in agile development or agile management are neither airline pilots nor surgeons, but we deal with complex projects involving many people and teams--and lots of rapidly changing details where evil lurks. Simple, customizable checklists are highly effective in slaying the complexity devil.
How do we begin with the acceptance criteria-driven development(ACDD) approach? There is no separate agile event or artifact required to adopt this process. The events we have been following for agile practices are enough. Following are the activities to be performed in agile events to get started.
Within a sprint, if you don't get the user stories right, it affects development, testing and the outcome of the sprint, and it takes a lot of effort to fix this later.
The project management landscape is changing. As our projects are becoming more challenging, it is impossible to determine the status or health of a project from just time and cost alone. Yet this is what we tried to do for more than five decades. Now we are beginning to recognize the need for additional metrics and KPIs.
Achieve more using prioritization and creativity.