ASSIGNMENT#1

McMaster University Bachelor of Technology

ENG TECH 3RQ3 – Software Requirements and Specification
Problem 1: Agile Responsiveness (/5)
There are a number of differences between the classical management model and the agile
management model in terms of team structure and workflow. Which of these do you personally
consider to be the ‘key’ difference that allows for agile projects to take on constantly changing
requirements? Why?
➢ The key difference that allows for agile projects to take on constantly changing requirements is
the flexibility to switch gears between task at hand to complete the project. The classical
management model also has minimal communication between teams completing different task
whereas there is more collaboration between team when it comes to agile management.

Problem 2: Long Term Planning (/15)

Agile is often considered to be better both for the long-term health of a project and for
improving the quality of work done by team members who are currently on the project. From
each perspective (project itself and a team member), give at least two reasons why the agile
methodology improves on classical models and briefly explain why it constitutes an
improvement. A total of four reasons should be given, 2 for the project perspective and 2 for the
team member perspective.
➢ From the project perspective, the two main reason agile methodology is better than classic
models are in agile the documentation as sufficient enough to understand and complete the
project whereas in classic model the documentation are way more detailed then it needs to be.
Another reason will be designing of one features will not require full requirements on the other
features to be completed, meaning there is no specific order to be followed to complete the
project as long as all the members are collaborating together to focus on task at hand.
➢ Form team member perspective, the first reason agile methodology is better than classic model
is the internal communication with different team of the project to get the work done and take
on changing requirement and the other one will be all the members of the team has a direct line
of commination with the customer whereas the classic model follows the specific order
methodology where there is a dedicated team to talk to customer.
Problem 3: Sample Situation (/15)
You are working at a small Startup as the sole developer on a new app that your leadership has
described as ‘Uber for cats’. You have arrived at a sprint start meeting where the next features
to be worked on are being decided. Your company’s Vice President, Angelica, is acting as the
scrum master and is leading the meeting. Last sprint you were able to complete some basic
server setup tasks but there are some major gaps you were planning to fill during this upcoming
sprint, however Angelica says that the priority is to build a customer-facing prototype and has
assigned you to complete several tasks for creating nice-looking and well branded web pages.
What are three things that your company is doing incorrectly according to the original goals of
agile project management? Explain why these issues do not meet with the original agile goals
and discuss what problems they can cause for the project and for the team.
➢ The first thing that the company is doing wrong by assigning new work of making customer-
facing prototype is not avoiding un-necessary work meaning if there are gaps in the server and
before that can be fix, the web-page will not function properly and after fixing the server again
the web page need to fix too.
➢ The second thing the company did wrong was used an excuse to cut corners where the new
features to be worked on are being decided in meeting instead they decided to change the
narrative by creating nice looking web page for the customer and thus lowering the design
standards.
➢ The third thing that the company did wrong was not testing the code at hand by the just moving
on to the next task after simple server setups giving it no time to debug all the problems.