Requirements GatheringFor Fun & (Non) Profit

NYC CampApril 2014

Jordan HirschSenior Digital Strategist

Phase2@tfish77

1Monday, April 14, 14

What Are Requirements,

Anyway?

2Monday, April 14, 14

Requirements are the things you need your new technology to accomplish-they are necessary for any kind of project-they allow you to communicate your vision to a builder who can implement your vision-without them, how do you know when you’re done?WHY DO WE CARE: you wouldn’t hire a general contractor to redo your kitchen with no idea about where the cabinets go

We can’t afford a Discovery phase!

Everywhere

-Everyone

“ ”

3Monday, April 14, 14

There’s never enough time or money-this might sound luxurious but it’s really essential

RISK: IF YOU SKIP YOUR REQUIREMENTS GATHERING/DOCUMENTING, YOU ARE ESSENTIALLY FLYING BLIND

Why Are We Here?

4Monday, April 14, 14

Establish goals & objectives early-even if you think you know, write it down-get stakeholder approval-goals provide a framework for decision-making and prioritization---when something new comes up, you can ask: “does this help us achieve our goals?” - if not, you can save it for later

RISK: iF YOU SKIP THIS, YOU HAVE NO FRAMEWORK FOR DECISION-MAKING OR FOR EXPLAINING YOUR DECISIONS TO OTHERS

What Matters Most?

5Monday, April 14, 14

Prioritize-shockingly, you can’t do everything!-minimum viable product - what is the least amount of functionality that can be called “successful” at launch?-you’re not santa claus - avoid wishlist sessions -prioritizing helps you focus your efforts-this is an ongoing process, not a 1-shot deal

RISK: IF YOU SKIP THIS, YOU WILL WASTE TIME AND MONEY ON THINGS THAT DON’T MATTER, AND YOU DON’T HAVE TIME & $ TO WASTE

When The Only Tool You Have Is Drupal A Hammer,Everything Looks Like A Nail

6Monday, April 14, 14

Focus on REQUIREMENTS, not TOOLS-requirements are about WHAT, not HOW-really pay attention to what you need, don’t get distracted by a shiny object-even Drupal may not be the right fit for you!-work with your vendor or your developers to adapt the tool to your users, NOT the other way around

RISK: IF YOU START WITH A TOOL IN MIND, YOU WILL END UP OVERLOOKING IMPORTANT REQUIREMENTS - OR FALL INTO A MINDSET OF “THE TOOL DOESN’T DO THAT”

Know Your Stakeholders

7Monday, April 14, 14

Talk to the right people-what are their technical abilities and limitations?-will they get trained?-do they have time to update this new website?-projects can have “hidden” stakeholders-think through your processes - who will have to use this tool?-forcing a technology on your stakeholders will lead to resistance, which can sink your efforts-don’t forget the executives-your users are stakeholders, too! - do user research

RISK: IF YOU SKIP THIS, YOU CAN END UP WITH A TOOL THAT NO ONE WANTS, OR THAT THEY CAN’T USE - AND YOU WILL FACE DISGRUNTLED USERS WHO CAN SINK YOUR PROJECT

You’re Only Human

8Monday, April 14, 14

Remember that you didn’t get everything-even the best requirements effort doesn’t get everything - why? - because humans make mistakes!-you’ll think of things later-things will change-priorities will shift-Solution? build in time in your project plan for ongoing requirements management-accept that requirements are not static

SPENDING TIME ON YOUR REQUIREMENTS HELPS YOU MITIGATE THE FACT THAT YOU ARE ALREADY STARTING AT A DISADVANTAGE BY NOT BEING PERFECT

Questions?

9Monday, April 14, 14

PHASE2TECHNOLOGY.COM

Thank You!

Jordan Hirsch | @tfish77

10Monday, April 14, 14