Learn SCRUM in Under 10 Minutes
Learn the SCRUM software development methodology in less than 10 minutes.
By the end of this fast-paced video, you’ll know about:
- burn-down charts,
- team roles,
- product backlogs,
- sprints,
- daily scrum
- and more…
by @hamids, http://www.axosoft.com
* * * * * * * * * * * *
Like what you read? Get hot news on the Agile-Lean community, upcoming webinars, case studies and tools you can use to help you be as Agile-Lean as possible….delivered right to your inbox weekly. No spam or junk mail. You can unsubscribe at any time.
..
very helpful video. I would have liked it to have “touched” on the basic needs for requirements definitions. Having the Backlog of Features listed and planned up front at beginning of the project. I am having a hard time trying to understand let alone Defend the need to know at the start of the project what are the “features” to be targeted for this project. There seems to be some differnece of opinions on “yes-changes are expected” VS Constant Additions (not changes) to the requirements therefore you never see the end of the tunnel…scope constantly growing…hard to get burn down chart when constantly adding new work….I guess this is a common problem with any project methodology.
Hi Leona,
This is a problem with any project methodology !
I am wrapping up a program of 20 projects, where we had a deadline, and all these “wish list” requirements. I told the teams “if you prioritize your requirements, then I’ll do as much as I can by the deadline”………guess what – we finish most of their lists way before deadline & allowed them to add more requirements to their “wish list”. They were amazed so much was done. And I used Agile techniques that we’ll teach you in our workshops coming up.
As a side note. Although Agile expect changes to occur….even if scope constantly grows – you have to manage your project within your project constraints (ie. Time, Scope, Cost, Quality, etc.) For example, if your deadline to create a product is 12/31, then guess what – you can only do so much by 12/31, and your backlog prioritized will guide you on what to work on until that deadline.
I tell my friends “You can ask me to design & build a computer chip in a day”, but that doesn’t mean it is possible !
Check out the VIRTUAL “hands-on” WORKSHOP coming up on 1/14/2009 that will teach you how to use Agile methods to gather requirements. You will walk away with the skill-set and tools to do this yourself.
–donna
@Leona,
Using and having an Agile mindset changes the way you think about your ‘project’. It’s true that you can get things added [or even subtracted] during the life of the project, but guess what: if you’re honest, that’s what happens with waterfall.
In the new world of doing only what you know at every instant of the project, you’ll have to prioritize for the next iteration the highest priority items, but you won’t have to be worried that you’ve missed much; there’ll be plenty of time to conjure up those missing items, or to get rid of those poorly thought through things that you’ve now realized you aren’t gonna need.
Relax. Try it.
regards, Hal Arnold
Thanks Hal,
I’m so glad you said to “Try it”……….so many times we let the fear of failure hold us back from trying something. So if Leona can find something to try it with – maybe not the entire project – but maybe with having daily standup’s…..build communiation with her team that way.
But be very careful not to use the daily standup as a status meeting. Teaching team to stay forward looking.
–donna
This was an excellent video that introduced all the concepts in a fun way. I would like to have other members of my team review this as well as sharing it with our R&D group. Thank you!