How do you set a project baseline?To set a project baseline, you must first determine the scope of your project. This can be done with a scope statement, which is a list of project objectives and deliverables. Break down all the work required to achieve these deliverables into individual tasks and subtasks with detailed descriptions. Show
Next, you must map out your project schedule with clearly defined due dates and a final deadline. A good tool to use here is a Gantt chart, which can be easily edited and adjusted according to changing deadlines. Estimate how long each task will take and allocate resources accordingly. Now, you should plan the total cost of your project. Take into account all relevant factors, including hourly rates, available resources, and varying PPC costs. Link this budget plan to your schedule to ensure the two are aligned. Your project baseline must be clearly outlined before you can move on to the next stage: stakeholder buy-in. Set up a meeting to present your plan, address any stakeholder concerns, and make any necessary edits. This is an important step in setting your project baseline, as it highlights any potential design flaws, which will be easier to fix before you start the project. When to Perform a BaselineBusiness analysts sometimes struggle with exactly when to define a requirements baseline. It’s an important decision because establishing the baseline has the following implications: Formal change control begins. Change requests are made against an established baseline. The baseline. therefore, provides the point of reference for each proposed change. Make sure your change control process and players are in place before you define any project baselines. Project managers determine the staffing levels and budgets needed. There are five dimensions to a software project that must be managed: features, quality, schedule, staff, and budget. Once the features and quality goals are defined in the baseline, the project manager adjusts the other three dimensions to accomplish the project’s objectives. It can work the other way, too. If staff, budget, and/or schedule are pre-established by external forces, the baseline composition is necessarily constrained to fit inside the project box bounded by those limits. Project managers make schedule commitments. Prior to baselining, requirements are still volatile and uncertain, so estimates are similarly volatile and uncertain. Once a baseline is established, the contents of the release should be sufficiently well understood so that managers can make realistically achievable commitments. The managers still need to anticipate requirements’ growth (per their requirements management plan) by including sensible contingency buffers in their committed schedules. Baselining requirements too early can push your change process into overdrive. In fact, receiving a storm of change requests after defining a baseline could be a clue that your requirements elicitation activities were incomplete and perhaps ineffective. On the other hand, waiting too long to establish a baseline could be a sign of analysis paralysis: perhaps the BA is trying too hard to perfect the set of requirements before handing them to the development team. Keep in mind that requirements elicitation attempts to define a set of requirements that is good enough to let the team proceed with construction at an acceptable level of risk. Use the checklist in Table 1 to judge when you’re ready to define a requirements baseline as a solid foundation for continuing the development effort. Table 1. Factors to Consider Before Defining a Requirements Baseline
You’re never going to get perfect, complete requirements. The BA and project manager must judge whether the requirements are converging toward a product description that will satisfy some defined portion of customer needs and is achievable within the known project constraints. Establishing a baseline at that point establishes a mutual agreement and expectation among the project stakeholders regarding the product they’re going to have when they’re done. Without such an agreed-upon baseline, there’s a good chance someone will be surprised by the outcome of the project. And software surprises are rarely good news. Which of the following has the most significant impact on the success of an application systems implementation?The overall organizational environment has the most significant impact on the success of applications systems implemented. This includes the alignment between IT and the business, the maturity of the development processes and the use of change control and other project management tools.
Which of the following is the area of greatest concern in an EDI process?One of the biggest risks applicable to EDI is transaction authorization. Due to electronic interactions, no inherent authentication occurs.
Which of the following is most important while evaluating a business case for acquisition of a new application?Which of the following considerations is the MOST important while evaluating a business case for the acquisition of a new accounting application? ROI to the company. The proposed ROI benefits, along with targets or metrics that can be measured, are the most important aspects of a business case.
Which among the following is most critical control for any application software?control risk. The correct answer is: B. detection risk.
|