Homework Help is Here – Start Your Trial Now!
Engineering
Computer Engineering
A small IT company you work for has been commissioned to develop a custom software for a large organisation. During the requirements gathering meeting, the following was established: Not all requirements are clear • End users will not be very involved in the project • Formal documentation is required during and at the end of the project. • The project is considered small in terms of duration and workload, hence small team is planned for with mainly a linear project plan • 2iterations are included due to the unclear project requirements • The software is considered non-critical to the organization • The organisation requires for existing processes to be used. In their paper, Andersen et al (2006) stated that the basic idea behind the traditional, rational and normative project approach is that projects are relatively simple, predictable and linear with clearly defined boundaries which all makes it easy to plan in detail and follow that plan without much changes. On the other hand, Agile project management approach is intended for projects characterized by high level of uncertainty, unclear project goals or incomplete and unpredictable requests, for which it could be assumed that will be significantly changed during the course of the project.

A small IT company you work for has been commissioned to develop a custom software for a large organisation. During the requirements gathering meeting, the following was established: Not all requirements are clear • End users will not be very involved in the project • Formal documentation is required during and at the end of the project. • The project is considered small in terms of duration and workload, hence small team is planned for with mainly a linear project plan • 2iterations are included due to the unclear project requirements • The software is considered non-critical to the organization • The organisation requires for existing processes to be used. In their paper, Andersen et al (2006) stated that the basic idea behind the traditional, rational and normative project approach is that projects are relatively simple, predictable and linear with clearly defined boundaries which all makes it easy to plan in detail and follow that plan without much changes. On the other hand, Agile project management approach is intended for projects characterized by high level of uncertainty, unclear project goals or incomplete and unpredictable requests, for which it could be assumed that will be significantly changed during the course of the project.

Computer Networking: A Top-Down Approach (7th Edition)
Computer Networking: A Top-Down Approach (7th Edition)
7th Edition
ISBN:9780133594140
Author:James Kurose, Keith Ross
Publisher:James Kurose, Keith Ross
Chapter1: Computer Networks And The Internet
Section: Chapter Questions
Problem R1RQ: What is the difference between a host and an end system? List several different types of end...
See similar textbooks
icon
Related questions
Question

Using the attached scenario.

The team is debating whether to use Scrum or Kanban methodology to
implement the Agile part of the project. You have decided to prepare a short
presentation highlighting advantages, disadvantages, tools or artefacts as well as how each methodology embraces changing scope.
Compare Scrum to Kanban methodologies then recommend to the team the
ideal methodology choice for this project. :

A small IT company you work for has been commissioned to develop a custom software for a large organisation. During the requirements gathering meeting, the following was established: • Not all requirements are clear • End users will not be very involved in the project • Formal documentation is required during and at the end of the project. • The project is considered small in terms of duration and workload, hence small team is planned for with mainly a linear project plan 2 iterations are included due to the unclear project requirements The software is considered non-critical to the organization • The organisation requires for existing processes to be used. In their paper, Andersen et al (2006) stated that the basic idea behind the traditional, rational and normative project approach is that projects are relatively simple, predictable and linear with clearly defined boundaries which all makes it easy to plan in detail and follow that plan without much changes. On the other hand, Agile project management approach is intended for projects characterized by high level of uncertainty, unclear project goals or incomplete and unpredictable requests, for which it could be assumed that will be significantly changed during the course of the project .
Transcribed Image Text:A small IT company you work for has been commissioned to develop a custom software for a large organisation. During the requirements gathering meeting, the following was established: • Not all requirements are clear • End users will not be very involved in the project • Formal documentation is required during and at the end of the project. • The project is considered small in terms of duration and workload, hence small team is planned for with mainly a linear project plan 2 iterations are included due to the unclear project requirements The software is considered non-critical to the organization • The organisation requires for existing processes to be used. In their paper, Andersen et al (2006) stated that the basic idea behind the traditional, rational and normative project approach is that projects are relatively simple, predictable and linear with clearly defined boundaries which all makes it easy to plan in detail and follow that plan without much changes. On the other hand, Agile project management approach is intended for projects characterized by high level of uncertainty, unclear project goals or incomplete and unpredictable requests, for which it could be assumed that will be significantly changed during the course of the project .
Expert Solution
trending now

Trending now

This is a popular solution!

steps

Step by step

Solved in 2 steps

SEE SOLUTIONCheck out a sample Q&A here
Blurred answer
Recommended textbooks for you
Computer Networking: A Top-Down Approach (7th Edi…
Computer Networking: A Top-Down Approach (7th Edi…
Computer Engineering
ISBN:
9780133594140
Author:
James Kurose, Keith Ross
Publisher:
PEARSON
Computer Organization and Design MIPS Edition, Fi…
Computer Organization and Design MIPS Edition, Fi…
Computer Engineering
ISBN:
9780124077263
Author:
David A. Patterson, John L. Hennessy
Publisher:
Elsevier Science
Network+ Guide to Networks (MindTap Course List)
Network+ Guide to Networks (MindTap Course List)
Computer Engineering
ISBN:
9781337569330
Author:
Jill West, Tamara Dean, Jean Andrews
Publisher:
Cengage Learning
Concepts of Database Management
Concepts of Database Management
Computer Engineering
ISBN:
9781337093422
Author:
Joy L. Starks, Philip J. Pratt, Mary Z. Last
Publisher:
Cengage Learning
Prelude to Programming
Prelude to Programming
Computer Engineering
ISBN:
9780133750423
Author:
VENIT, Stewart
Publisher:
Pearson Education
Sc Business Data Communications and Networking, T…
Sc Business Data Communications and Networking, T…
Computer Engineering
ISBN:
9781119368830
Author:
FITZGERALD
Publisher:
WILEY
SEE MORE TEXTBOOKS