What are Elicit Requirements?

954 Words2 Pages
bulb-icon

Recommended: Project Management: Perspective, Planning and Implementation

Eliciting requirements sounds like the easiest task in the world. Ask questions to users or the business and get the requirements. In the real world this process is one of the most difficult parts of the project. If the requirements are not fully understood, it will create issues in your analysis and decrease your chances of efficiency and success. If you can properly elecit, verify, and validate the requirements, you will lay the foundation for an effective project.
The phrase "gather requirements" does not express the real mission of the IT project requirements. You are not a cave man, you do not gather requirements, they are not just laying around on the ground for you to pick them up. "Elicit" is the word that better matches the job. Elicit refers to an active role in IT requirements consolidation, verification and validation. Merriam-Webster defines elicit as; “To draw forth or bring out (something latent or potential), To call forth or draw out (as information or a response)”. “it is the responsibility of project stakeholders to provide, clarify, specify, and prioritize requirements. Furthermore, it is the right of project stakeholders that developers invest the time to identify and understand those requirements. This concept is critical to your success as an agile modeler, it is the role of project stakeholders to provide requirements, it is the role of developers to understand and implement them.” (Ambler, 2011)
When I was a young soldier I was given a mission. Before we left we had to read back everything we heard to make sure we understood the plan to its original intent. This may seem crude but it ensured every person on the team had the same picture of success in their head. If IT managers and stakeholders could hav...

... middle of paper ...

...iton are so important in each method and why one method isn’t better than another. Depending on the situation, you may choose to use more than one method but the preparation is the same.

Works Cited

Gottesdiener, E. (2008). YAGNI Your requirements documentation. EBG Consulting, Inc. Retrieved 23 December, 2013 from, http://www.requirementsnetwork.com/system/files/YAGNI.pdf
Sauter, V. (2007) Feasibility. Retrieved 23 December, 2013 from, http://www.umsl.edu/~sauterv/analysis/feasibility.htm
Ambler, S. W. (2011). Agile requirements modeling. Agile Modeling. Retrieved 23 December, 2013 from, http://www.agilemodeling.com/essays/agileRequirements.htm
Usability.gov (N.D.) Evaluate your current site: Usability methods. US Department of Health and Human Services. Retrieved 23 December, 2013 from, http://www.usability.gov/methods/analyze_current/index.html.

Show More
Related

  • Work Breakdown Structure Essay

    787 Words  | 2 Pages

    A work breakdown structure is a key project deliverable that organizes the team 's work into manageable sections. The Project Management Body of Knowledge. defines the work breakdown structure as a "deliverable oriented hierarchical decomposition of the work to be executed by the project team”. Basically the work breakdown structure is something that is put together which defines the scope something that project team can understand. On the other hand, project requirement is kind of a document which tell management, what has to be produced and the exact date of completion. It also is based on responsibility factors. Requirements are the expectations which the product need to fulfill. Requirements are collected from the customer, stakeholders and Sponsor.

    Read More

  • Caregroup Case Study

    806 Words  | 2 Pages

    2. Do not let any one individual in your IT group become the sole point of failure. Correct assessment; ironically it was a knowledge management system that led to the crash of the network. Succession planning is key ingredient to success for businesses. 3.

    Read More

  • Description Of The NASA Space Shuttle Program

    1719 Words  | 4 Pages

    objectives vital to the successful completion of the project (history would prove otherwise). In addition,

    Read More

  • Compare And Contrast Of: Four Stage Team Performance Model & The Drexxler/Sibbet Team Preformance Model

    1499 Words  | 3 Pages

    “The team is faced with creating cohesion and unity, differentiating roles, identifying expectations for members, and enhancing commitment. Providing supportive feedback and fostering commitment to a vision are needed from the team leaders (Developing Management Skills).” ... ... middle of paper ... ...

    Read More

  • The Initial Component of Module QF5000

    915 Words  | 2 Pages

    I found working within a team enabled us to spread responsibility and we determined ...

    Read More

  • Team Dynamics

    1098 Words  | 3 Pages

    People tend to have different ideas of what constitutes good communication. It is important to define communication and ways to build effective communication within teams, in order to have a successful team output. Some people think of communication solely as speaking, but it should be stressed that up to 90% of communication can be listening to fellow team members, and only 10 % talking (Lay, 2008). There are different aspects of effective communication that should be discussed by the group when it is initially formed. In order for teams to be successful, they should define how they will communicate with each other, and define the tasks that will set out by the team.

    Read More

  • The System Development Lyfe Cycle Phases

    1089 Words  | 3 Pages

    After the systems planning is complete, the next course of action is the systems analysis phase. This phase includes defining the requirements of the system. This means that the team must conclude what the system needs to do in order to satisfy the users. This is done by forming a requirements...

    Read More

  • FINANCIAL MANAGEMENT

    1058 Words  | 3 Pages

    Talking directly to the stakeholders will help answer most of these key questions. For IT projects meeting the key stakeholders in a forum to review progress on the project is key to its success. Therefore a well drawn up project plan will ensure that there is enough representation of the stakeholders at the regular project review meetings.

    Read More

  • Rational Unified Process

    1248 Words  | 3 Pages

    Given the time, it takes to develop large sophisticated software systems it not possible to define the problem and build the solution in a single step. Requirements will often change throughout a projects development, due to architectural constraints, customer’s needs or a greater understanding of the original problem. Iteration allows greater understanding of a project through successive refinements and addresses a projects highest risk items at every stage of its lifecycle. Ideally each iteration ends up with an executable release – this helps reduce a projects risk profile, allows greater customer feedback and help developers stay focused.

    Read More

  • Importance Of Quality Improvement In Healthcare

    1233 Words  | 3 Pages

    Define the current situation - break down problem into component parts, identify major problem areas, develop a target improvement goal

    Read More

  • AMP Canada Case Study

    2642 Words  | 6 Pages

    For this project, a Request for Proposal (RFP) will be issued in order to solicit proposals from various SAP business partners’ vendors which describe how they will meet the requirements, deadline and the cost of implementing the finance

    Read More

  • Project methodology

    1778 Words  | 4 Pages

    These are the usual questions asked at the start of any project, and the answers are the building blocks of project management - defining what we want to do and working out the best way we can do it. When carrying out a project it is important for the project manager to decide on a method of undertaking the project. There are a large number of different methods that can be adopted, these are called project methodologies, they can be used to assist in the success of a project, the chosen methodology will determine how the project is initiated and also executed until completion.

    Read More

  • Implications Of Quality Essay

    881 Words  | 2 Pages

    As per ISO 9000: “Degree to which a set of inherent characteristics fulfills requirements.” The standard defines requirement as need or expectation.

    Read More

  • Overview of Agile Methodology

    1555 Words  | 4 Pages

    Agile software development is a group of software development methods based on iterative and incremental development, where requirements and solutions evolve through collaboration between self-organizing, cross-functional teams. It promotes adaptive planning, evolutionary development and delivery, a time-boxed iterative approach, and encourages rapid and flexible response to change.

    Read More

  • Role Of A Business Analyst In Agile

    850 Words  | 2 Pages

    Which leads to one job role that seems tailor-made for the business analyst. Once you start discussing requirements management in an Agile environment, you inevitably end up discussing the role of the Product Owner. The Product Owner is responsible for ensuring that the team is focused on delivering products that have real business value -- that address the trinity of problems, issues, and goals. That definition brings us right back to the business analyst playing "a role in aligning the designed and delivered solutions with the needs of the stakeholders.”

    Read More

More about What are Elicit Requirements?

Open Document