Unit 4 Software Development 011 Powerpoint

Which of the following would be most appropriate when reviewing the number of changes to a project plan?

• Identifying how many developers joined the project

• Calculating total project expenditure

• Comparing initial and final versions of the Gantt chart

• Conducting a usability test of the completed software

A project experienced 11 changes to task durations, mostly during the testing phase. What is the most likely conclusion?

• The development team lacked experience in user interface design

• Testing was underestimated during initial planning

• The SRS was not signed off by stakeholders

• The hardware requirements were unclear

Which of the following reasons for changes in a project plan is most likely considered unavoidable?

• Late stakeholder request to redesign the interface

• Developer requests to switch programming languages

• API integration fails due to third-party platform removal

• Client dissatisfaction with user manual layout

Why is it important to record the reasons for changes to a project plan?

• To reduce the amount of testing required

• To help evaluate whether planning errors or external factors were involved

• To increase the number of project meetings

• To avoid documenting lessons learned

Which tool would be most appropriate for tracking and justifying changes made to a project plan?

• Entity-relationship diagram

• System flowchart

• Project journal or version control log

• Data dictionary

A milestone was delayed by four days due to a developer being unavailable. Which category does this reason fall under?

• Scope creep

• Personnel issue

• Technical problem

• Data loss

The addition of a new report generation feature halfway through development best reflects:

• A. A miscalculation of estimated task durations

• B. A personnel issue affecting critical tasks

• C. Scope change initiated by stakeholders

• D. A testing error in the evaluation stage

Which of the following represents a positive impact of a change on a project?

• Increased development cost with no functional improvement

• Reduced testing time, resulting in missed bugs

• A delay in deployment that led to higher user satisfaction due to better usability

• Rewriting major components that introduced new compatibility issues

Which statement best reflects the relationship between change frequency and planning quality?

• More changes always mean poor initial planning

• Fewer changes guarantee a better end product

• A balanced number of necessary changes may reflect effective responsiveness

• The number of changes is irrelevant if the system works

Which combination of change type and impact would suggest a neutral effect on the project?

• Change: Delayed deployment. Impact: Missed milestone.

• Change: Removed non-critical feature. Impact: Users complained.

• Change: Adjusted deadline for documentation. Impact: No delays and improved quality.

• Change: Added analytics tool. Impact: Caused security flaw.