Agile software development methodologies like Scrum are easy to learn, but hard to master. It's easy to get some of the details wrong. This could keep your team from receiving all the benefits the framework has to offer, or worse, lead to poor communication and defects. This screencast will walk you through Agile best practices, with a discussion of some of the pitfalls, and ways to get your team back on track.
This video will be most helpful to viewers with some experience working in Scrum or another Agile framework. If you're new to this style of software development, check out the Resources section for some helpful links that will get you up to speed!
Many thanks to our sponsor, Atlassian, for helping us make this screencast available to everyone for free! Be sure to check out their awesome tools to help your team down the Agile path:
Bitbucket: Unlimited private Git repositories to collaborate on your code in the cloud. Free for 5 users.
Agile planning with GreenHopper: Go agile with ease, whether you're a seasoned Agile team or just getting started. The tool of choice for thousands of teams will help you avoid anti-patterns like the ones highlighted today.
Title should be changed to say "Scrum" instead of "Agile", particularly since the content is littered with references to scrum terminology. For example, the agile manifesto makes no reference to the concept of timeboxing (ala sprints or iterations), though they are a centerpiece of scrum. Not a fan of the "best practices" concept either, as different environments/contexts require different approaches. Better would be a survey of various practices that work within given contexts.
Thanks for the informative video! Very useful knowledge.
Always having this idea in mind: "Learning to say -NO-, earlier, will reduce future trouble in saying -YES-" Nice job, Jay Gavren, those examples seemed to be my daily issues!
Very well said about the practical problems that we are facing regularly during the product development. Thanks for this awesome video.
PO needs 3 things. Authority, Time, and Product knowledge
Good video.
However, I couldn't get it to work at all in Chrome (played for 6 secs) Only IE was truly smooth.
Nice work! It seems like we are doing things right at CrowdInt.com :D Yeeeiii! by the way... talking about retrospectives... try Retrospectus ;)
Hi,
A good overview of some problems in scrum here. The only thing is that I don't believe is that a product owner can be someone just plucked from another department. A PO is more than just someone with domain knowledge, they need a fair chunk of skills and knowledge associated with the role of a BA too.
With a decent product owner, you wouldn't need to bother the stakeholders very often.
Awesome episode. It's so easy to let the basics slip when you're under pressure to release. I've just reminded our guys I haven't seen an end of iteration demo for the last 3 iterations. Knuckles rapped - especially mine.
Good one! I'd love to see more content like that.
Thank you!