« Four-eared Cats| Main | How to "get" Philosophy »
Test Your Agile Knowledge
How's your agile knowledge? Try this short quiz and rate yourself.
- What's the recommended iteration size for an agile project?
- 2-4 weeks
- 1-8 weeks
- 4-12 weeks
- 4 weeks or under
- What are the three project roles in Scrum?
- Coach, Programmer, and Project Manager
- Developer, Scrum Master, Product Owner
- Product Owner, Project Manager, and Developer
- Scrum Master, Scum Lord, Scrum Owner
- Developer, Scrum Master, Project Manager
- How are Scrum and Agile related?
- Scrum tells us everything we need to know to run Agile projects
- Agile is just a looser form of Scrum
- You have to pick to do either Agile or Scrum. You can't do both
- Scrum is a project management framework that can be used for agile projects
- When are requirements completed in iterative projects?
- Once the product owner says so
- When the project is completed
- Once the code is written for the story
- They're never completed
- What's the tool we use in agile projects to understand and agree on what the system is supposed to do?
- Stand-ups
- Waterboarding
- Face-to-face conversations
- MS Word, or other document-writing tool
- The agile staff of compliance
- When does the Product Owner get to change the requirements?
- At any time the product owner can change the backlog, but only during iteration planning does the team size and buy stories for the next iteration
- He can add requirements at any time, but he cannot delete requirements unless it is part of a retrospective
- Only during a retrospective
- Once the requirements are written down, they cannot be changed until the next iteration
- Requirements are like the wind, when are they not changing?
- At any time the product owner can change the backlog, but only during iteration planning does the team size and buy stories for the next iteration
- What's the purpose of an Agile Coach?
- To take all of your money
- To provide hands-on experience whenever you need so that you don't have to make so many mistakes
- To help you plan for how to change your organization to make it more agile
- Somebody to blame when the project goes south
- An expert in how perfect agile teams work and how to make your team perfectly agile
- To take all of your money
- What's the three questions in a stand-up?
- What was I working on?
- What am I going to be working on?
- Who needs to help me?
- Where am I?
- How much longer do I have?
- What are my obstacles?
- What's the best team size for an Agile project?
- More than you think
- 8-15 people
- Anything under 30 people
- 5-7 folks
- As few people dedicated at 100% as absolutely necessary and not a person more
- Can a CMMI shop, like the one that does Space Shuttle code, be Agile?
- No. Agile is about reducing paperwork, therefore paperwork-heavy, bureaucratic projects cannot be agile
- Yes. Agile is about minimizing overhead. Some projects may still require a lot of it
- It can be agile, but only if they also follow the best practices of Scrum
- Can I phone a friend?
- What's the famous sequence of numbers that some practitioners use to score stories?
- 4, 8, 15, 16, 23, 42
- The Fibonacci Sequence
- Archimedes' sequence(s) for p
- The closing sequence to the Titanic
- The Mean Square Root sequence
- If you change the definition of "done" to mean something less, just so you can get something completed, what are you incurring?
- The Wrath of Kahn
- Backlog resizing
- Technical debt
- Dependency injection, where work that depends on unfinished work creates a block
- Premature optimization
- How long has Agile/Iterative-Incremental Development been around?
- Since about 2000
- Since about 1990
- Since about 1980
- Since dinosaurs roamed the earth
- Since there have been complex projects to deliver
- Is it absolutely required that you have a single product owner for a team to be truly agile?
- Yes
- No
- Given these items, which one is the most important in an agile team?
- Delivering working code each iteration
- Collaborating cross-functionally
- Identifying a visible business owner who actively participates
- Being able to forecast when items in the backlog will be delivered
- The team owns their estimates and decides what work they can accept each iteration
- The team continuously identifies risks/issues and acts on them immediately
- Is Agile only for software projects?
- Yes
- No
- Stuff we need to make the system to in order for the Product Owner to be happy. We put that into a list called the what?
- Work queue
- Backlog
- Frontlog
- Issue list
- Story Board
- Bob
- What's the thing we do at the beginning of a project to 1) onboard the team, 2) create the initial backlog, and 3) have the business set up the project for success?
- Project Genesis
- Iteration Negative One
- The Great Beginning
- Inception
- We don't do that in Agile
- When is extending an iteration deadline okay?
- Only during holidays
- Never
- It can happen any time
- Only when mission-critical stories cannot be completed in the original sprint length
- Use Cases and User Stories are completely different things, right?
- Use Cases is an analysis technique, User Stories are placeholders for some kind of analysis conversation which might be use-case based, so no, they are not different
- Use-Cases are a lot of documentation. User Stories are much lighter. So yes, they are different
- User stories are about conversations. Use cases are about paperwork. So yes, they are different
- It depends on how you use them
- What's the best philosophy for an organization to us in implementing Agile?
- Stoicism
- Pragmatism
- Existentialism
- Epicurianism
- If you are a truly agile, high-performing team, that means that you're going to have very few meetings and hand-offs, right?
- Yes
- No
- True or False, items in the backlog are the requirements for an Agile project
- True
- False
- True or False, to be truly Agile, you should use points instead of hours for story estimation
- True
- False
- What's the answer to Life, The Universe, and Everything?
- More beer
- Cats
- 42
- 56
- Do coaches have to mention the Agile Manifesto every time we talk about agile?
- No. The manifesto is just a marketing tool. It's a way of thinking, not a set of slogans
- Yes. It's an elaborate kick-back scheme
- Only if I am brainless
- What's that?
Bonus Question
Answers
1.D 2.B 3.D 4.B 5.C 6.A 7.B 8.A, B, F 9.E 10.B 11.B 12.C 13.E 14.B 15.F 16.B 17.B 18.D 19.B 20. A or D 21.B 22.B 23.B 24.B 25.C 26. A
Explanations for tricky items coming in a future post
Scoring:
- 23+ You are an Agile God
- 20 - 23 You've got it
- 17 - 20 You know enough to be dangerous. Danger Will Robinson!
- 14 - 20 You're off to a good start. Keep at it.
- Less than 14: Hey, we all gotta start somewhere
Leave a comment