NEW
Font size
WorksheetsLEARNING OUTCOME 1 – Traditional vs Agile Methodologies
Total questions: 40
Worksheet time: 20mins
The traditional SDLC is also commonly known as:
Iterative model
Waterfall model
Spiral model
Incremental model
Which of the following is NOT one of the four core values of the Agile Manifesto?
Customer collaboration over contract negotiation
Working software over comprehensive documentation
Following a plan over responding to change
Individuals and interactions over processes and tools
A key strength of the traditional Waterfall approach is:
Easy accommodation of requirement changes
Well-suited for projects with unclear requirements
Strong emphasis on early planning and documentation
Frequent delivery of working software
Which is a common weakness of Agile methodologies in regulated industries?
Too much documentation
Lack of predictability and formal audit trails
Fixed scope and timeline
No customer involvement
The main reason organizations resist moving from traditional to Agile is usually:
Fear of too much documentation
Cultural and mindset shift required
Lack of tools
Excessive planning
Which methodology is best when requirements are stable and regulatory compliance is critical?
Scrum
Kanban
Traditional/Waterfall
Lean
In Agile, the “Definition of Done” is primarily used to:
Finalize the project contract
Ensure a user story meets quality criteria before it is accepted
Create detailed design documents
Assign blame when something fails
Which ceremony is unique to Scrum and not typically found in traditional methodologies?
Requirements sign-off meeting
Sprint Retrospective
Final acceptance testing
Project closure report
The “cone of uncertainty” is narrowest:
At the start of a traditional project
At the end of a traditional project
Throughout an Agile project
During the testing phase only
Which Agile practice helps reduce risks through frequent feedback?
Big Design Up Front (BDUF)
Time-boxed iterations/sprints
Detailed Gantt charts
Change control boards
In the Waterfall model, testing typically begins only after the entire system is built.
True
False
Agile methodologies require comprehensive documentation before development starts.
True
False
The Product Owner in Scrum has the authority to cancel a sprint if goals become obsolete.
True
False
One of the advantages of Agile is lower overall cost due to early detection of issues.
True
False
Traditional methodologies generally provide better cost and schedule predictability than Agile.
True
False
Agile teams are usually cross-functional and self-organizing.
True
False
Moving from Waterfall to Agile often requires changes in performance evaluation and reward systems.
True
False
The traditional approach is more suitable when the customer cannot be involved throughout the project.
True
False
“Working software is the primary measure of progress” is an Agile principle.
True
False
In traditional SDLC, scope creep is easily managed because of flexible requirements.
True
False
The three main categories in the DVF framework are:
Design, Viability, Functionality
Desirability, Viability, Feasibility
Development, Validation, Funding
Demand, Value, Finance
Which feasibility type asks “Will the system work within the existing organizational culture?”
Technical feasibility
Operational feasibility
Economic feasibility
Schedule feasibility
Cost-Benefit Analysis, ROI, NPV, and Payback Period are part of:
Technical feasibility
Economic/Financial feasibility
Legal feasibility
Operational feasibility
Which investigation technique is most useful for gathering quantitative data from a large audience?
One-on-one interviews
Workshops
Questionnaires/Surveys
Prototyping
“Can we build it with the available technology and skills?” refers to:
Technical feasibility
Schedule feasibility
Resource feasibility
Operational feasibility
A project with negative NPV would normally be considered:
Highly desirable
Economically unviable
Technically impossible
Operationally perfect
Which of the following is typically NOT included in a feasibility report?
Risk analysis
Detailed database schema
Recommended option
Cost estimates
Schedule feasibility primarily evaluates:
Whether the project can be completed on time with available resources
Whether users will accept the system
Whether the budget is sufficient
Whether the technology exists
The primary purpose of a business case is to:
Provide detailed technical specifications
Justify the investment and gain approval/funding
Train end users
Write test cases
Observation as an investigation technique is particularly useful for:
Understanding actual current processes and identifying inefficiencies
Getting opinions from senior management
Collecting statistical data
Validating system performance
A feasibility study is conducted during the initiation or planning phase of a project.
True
False
Technical feasibility only considers hardware requirements, not human skills.
True
False
A system can be technically and economically feasible but still fail due to low operational feasibility.
True
False
“Desirability” focuses on whether users actually want or need the proposed solution.
True
False
Legal and ethical feasibility is sometimes considered a separate category in modern business cases.
True
False
Prototyping is never used during the feasibility stage.
True
False
Payback period measures how long it takes to recover the initial investment.
True
False
A high-risk project is automatically infeasible.
True
False
The business case is usually created after the project has been fully approved and funded.
True
False
Interviews and focus groups are examples of qualitative investigation techniques.
True
False
