Collecting the requirements to start your project
BY: NEISHA SANTIAGO
Are You Looking for Success in Your Project? Check out this 10 Esessential Requirements Before Starting Your Project:
- Establish Your Goals
Without clearly established goals and objectives, you cannot have a clear idea of where you are going, and you cannot make clear decisions. Determine if what you are looking for, helps you reach a goal, or meets a goal. If so, it is probably a good option.
- Document Everything
Document all the essential details when you are in the middle of an interview or meeting related to your project. At first, we thought we understood all, but after a few days, everything became confusing and complicated to understand, so it is crucial that you organize and take notes of everything discussed regarding your project.
- Be Transparent With Documentation and Your Team WorkIt is clear that you understand the requirements but interested parties also need to know where you are going. After each meeting, update your notes, clean and rewrite everything so that it is readable and understood by all parties. This transparency guarantees you better communication and commitment with your team. The benefit you will get will be more significant in the long term.
- Talk to The Right Person
A project can usually have unknown stakeholders. Ask probing questions in your opening and meetings to try and get to who the real users are. Typically, those people are not going to be the primary decision-makers, but their buy-in is fundamental to a successful project.
- Do Not Make Assumptions
Don’t assume that you know everything, even if it appears obvious. Things that seem to be simple end up getting more complicated than expected, so don’t be confident with a project until all the project members have reviewed all the points.
- Always Confirm
Merely sharing your notes with an interested party is excellent, but much more important is having a quick review with them and getting their official approval. Always get the real confirmation from your stakeholders that you are following the requirements correctly, then continue.
- Be an Active Listener
Making someone feel heard is one of the best things you can do for them. However, it goes beyond just hearing what they say: you must also attend to what they don’t say, reading their body language. Active listening and is a necessary element of successful requirements gathering. Do not assume that you always understand all; recognize signs that reveal discomfort points, unexpressed goals, and assumptions.
- Focus on The Requirements, Not on The Tools
You are gathering requirements that you are focusing on and listening to what your stakeholder wants, not what your tool-of-choice appears to do best. You need to adjust the product to the user, not the other way around. Listen and gather first, then decide where the gaps are between your stakeholder’s requirements and any existing product you may have in mind.
- Prioritize Your Product
It is easy for requirements gathering to turn into dream list collection sessions, where involved parties tell you everything they want. The point is not to ignore that information but rather prioritize what you are listening to and outline what is in scope for your first release.
- Remember You Didn‘t Get Everything
Don’t feel distressed; Even the best requirements collector will lose things. Why? Because we are not perfect, in fact we all make mistakes. Things will change. The preferences will change. Taking time to manage the requirements throughout the project can help you stop the advance of the scope before it starts, and guarantee that your team always concentrates on the correct priorities that meet the actual requirements.
“If everyone is moving forward together, then success takes care of itself.”