IT Elec1 - Agile Programming Prelim Exam

A software development methodology that focuses on waterfall model.

A project management approach that focuses on iterative development and collaboration.

A traditional project management approach.

A project management approach that focuses on documentation and strict plans.

Contract negotiation over customer collaboration.

Following a plan over adapting to change.

Comprehensive documentation over working software.

Individuals and interactions over processes and tools.

A methodology that requires strict adherence to all project requirements, with no room for changes or adjustments.

A way of thinking and approaching work that values flexibility, collaboration, adaptation, and continuous improvement.

A mindset that only focuses on speed and delivering quick results, without considering quality or long-term goals.

A specific set of rules and processes to follow in project management.

A fixed and rigid approach to work that focuses on adhering to plans and processes.

Adopting a one-size-fits-all approach for every project.

Adhering strictly to the initial plan without any adjustments.

Completing all tasks as quickly as possible, regardless of quality.

Responding to change over following a plan.

Having a hierarchical structure with clear authority and decision-making.

Maintaining a rigid and fixed project scope.

Meeting strict deadlines and milestones.

Delivering customer value.

Following a linear and sequential project plan.

Minimizing costs and resource utilization.

Focusing primarily on documentation and processes.

Avoiding any form of collaboration.

Placing individual tasks above team efforts.

Embracing change.

Adhering strictly to established plans.

To enhance processes, products, and outcomes over time.

To achieve the highest level of efficiency from the beginning.

To minimize the need for collaboration and teamwork.

To ensure a fixed and unchanging approach to work.

To illustrate adherence to established plans and processes.

Teams that only focus on individual tasks and responsibilities.

Teams that have the autonomy and responsibility to make decisions and organize their own work.

Teams that ignore collaboration and work independently.

Teams that rely on a hierarchical structure for decision-making.

Teams that strictly follow pre-defined rules and processes.

To deliver high-quality, valuable software iteratively and incrementally.

To complete all project tasks as quickly as possible.

To prioritize individual tasks over team collaboration.

To strictly adhere to a predefined project plan and timeline.

To deliver minimal viable products without considering quality.

To assign blame for any project setbacks or failures.

To enforce strict adherence to project plans and processes.

To track individual progress and accomplishments.

To eliminate all changes and adjustments in a project.

To reflect on the team's performance and identify areas for improvement.

To provide visibility and open communication throughout the project.

To prioritize individual goals over team collaboration.

To avoid sharing progress or feedback with stakeholders.

To hide information and limit communication between team members.

To strictly enforce rules and processes without explanation.

To discourage communication and idea-sharing.

To prioritize competition among team members.

To limit collaboration and favor individual work.

To assign tasks based on strict hierarchies.

To encourage cross-functional teamwork and shared responsibility.

2005

1999

2001

2003

Ken Schwaber

Ward Cunningham

Jeff Sutherland

Alistair Cockburn

Responding to change over following a plan

Completing all tasks before moving to the next phase

Following a strict plan over responding to change

Maximizing documentation