Requirements Team Quote by Andrew Hunt

“The success of the documentation efforts lies in the users being able to correctly locate and use the resolutions to their issues on time…

— Suyog Ketkar

What I found over the years is the most important thing is for a team to come together over a compelling vision, a comprehensive…

— Alan Mulally

“to frame the decision, asking questions about the data and the methodology, working to understand the results, and using them to improve outcomes for…

— Anonymous

“what’s most important is that the information we display is up to date, and that we constantly revise what we measure to make sure…

— Gene Kim

You need to set near-term milestones. Put the assumptions down on paper, and make it to your vision or ultimate product. Your team has…

— Tony Fadell

“You must be able to explicitly say who you are building your thing for. You must know what you are aiming for—you’ll miss otherwise.…

— Ryan Holiday

“Your product roadmap should slot right in between your company vision and your more detailed development, release, and operational plans.”

— C. Todd Lombardo

“the most important part of design is finding all the issues to be resolved. The rest are details”

— Soumeet Lanka

“the importance of putting your team first, ahead of your personal statistics and recognition.”

— Satya Nadella

“These needs, then, are just as real as any other requirements; we refer to them here as required constraints or design constraints, and they…

— Derek Hatley

“Communicate the plan clearly and have clear metrics conveying whether you are progressing according to it.”

— Ray Dalio

Making lists of reasons was sometimes a good way to figure things out.

— Lois Lowry