Teams run into trouble when they adopt agile practices without really knowing why they are doing them. This can happen when people who’ve been told to use iterations (sprints) still don’t understand why. And when they act on these statements, they unknowingly undermine their efforts to use agile. What can we do?
Just because you are working in a waterfall organization doesn't mean you can't be Agile. Join Dave Prior as he walks you through a case study on implementing Scrum in a waterfall environment. He offers some key practices and data points that will enable you to be successful in both keeping the team productive and providing the information needed to build trust and confidence with the Project Sponsors and Senior Executives you need to support your Agile implementation.
Learn From Others
In an ideal world, a cross-functional Scrum team must be fully focused on Scrum. The team is also expected to hear a voice of one customer only: the product owner. But what happens when reality intervenes and you get pulled in other directions? As our two-part series concludes, we look at the remaining two ways of interrupting Scrum sprints--and share what can be done about them.
In an ideal world, a cross-functional Scrum team must be fully focused on Scrum. The team is also expected to hear a voice of one customer only: the product owner. But what happens when reality intervenes and you get pulled in other directions?
Scrum Alliance’s 2015 version of the State of Scrum has just been published. It contains some very interesting insights that we should all be aware of.
There are great opportunities for growth and deviation outside the standard agile models for stable teams who want to evolve further. This article tells the story of one team that did just that--and what other people can learn from it.
The number of agile certifications available in the market keeps growing, and one must consider the unique needs of the inquiring company or individual to know what would be best for them. What factors should you consider? Do you even know the options available?
Have you ever entered a sprint taking on a user story that you later regretted? What can be done to prevent this frustration? Is there a technique that will prevent this from happening, or are these teams doomed to keep repeating their mistakes?
In its popular, standard form, the Daily Scrum (“the Standup”) hurts teamwork. Follow this PM to understand how and why the meeting causes that--and discover alternatives that work better.
|A.||Traditional teams may have a 15-20% contingency cushion in time and cost on their project estimates. Routinely subtract a similar agile contingency from the number of backlog items you accept to make sure you finish all planned work within a single iteration.|
|B.||Agile is expected to be flexible, and velocity can vary. Just complete what you can and adjust your velocity for the next sprint if you don’t finish all of the stories you committed to complete this time.|
|C.||Be sure you are acknowledging hours that team members will spend in Scrum ceremonies, personal time commitments and non-team directed organizational work before calculating the capacity for this iteration.|
|D.||Ask the ScrumMaster to speak to anyone on the team who did not finish his or her work during the previous iteration. This person is making the team look bad and should be disciplined if it happens again.|
A retrospective is a special meeting during which the team gathers after completing an increment of work to inspect and adapt their methods and teamwork. Retrospectives enable whole-team learning, act as catalysts for change and generate action. This article presents some of the reasons why the retrospective’s efficacy can fade over time and then discusses some interesting techniques to keep them lively.
As an experienced agile coach, this writer often gets asked about agile tactics and practices--what works and what doesn’t. There are no singular answers, but there are some generative behaviors and rules for agile done well. In this article, he explores a set of common anti-patterns that he sees in an effort to share what not to do in your agile journey.
Ask a Question
|PMI-ACP® Terms Relay Race !||VenkatramVasi M||Feb 12, '16 5:18 AM||0||61|
|Which certification should i choose?||Dhinesh Muralidharan||Feb 3, '16 11:36 AM||0||14|
|What PM methodologies increase project success rates?||Stéphane Parent||Jan 21, '16 7:05 AM||0||21|
|Agile Contracts and Compliance||Bryan Campbell||Jan 14, '16 10:45 AM||0||5|
|Scrum defintion and industry application||Udeme Akpan||Nov 29, '15 11:14 AM||0||5|
|SCRUM Certifications in Market||Suhail Iqbal||Sep 2, '15 3:47 AM||0||3|
|Scrum||arlene trimble||Jul 16, '15 5:53 PM||0||0|
|Scrum/Business Alignment||Kathy Sundholm||Jun 29, '15 4:53 PM||0||1|
|Examples of non-IT/software Scrum implementation and uses||Federico Varchavsky||Apr 16, '15 7:42 PM||0||3|
|Mark All Read|