week 2 assignment
docx
keyboard_arrow_up
School
Cumberland University *
*We aren’t endorsed by this school
Course
5131
Subject
Information Systems
Date
Dec 6, 2023
Type
docx
Pages
18
Uploaded by MatePuppyMaster3743
What are the main
differences between the
two versions of the JWD
Consulting case
study?
The differences are as
follow:
Firstly, the main
difference between pre-
initiation would be
determining roles and
deciding what
functionality would be
delivered as part of each
release, how many
sprints
will be required to
complete a release, and
how many releases of
software to deliver. In
the prescriptive
approach, only one
release of the software
would be made which will
be
at the very end.
Secondly, in prescriptive
approach the planning
process includes creating
a team charter,
WBS, Gantt chart, and list
of prioritized risks for the
whole project. In agile
approach, the
team follows a scrum
method; a preliminary
scope statement is
written and in place of a
WBS, high-level
descriptions of the work
to be completed would
be identified in the
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
- Access to all documents
- Unlimited textbook solutions
- 24/7 expert homework help
product and sprint
backlogs.
Thirdly, the team would
complete tasks each day
in both approaches, but
by using an
agile approach, the team
would produce several
iterations of a potentially
shippable
product.
Next, in the prescriptive
approach, a brief
progress report was
submitted each Friday.
However, in agile
approach, daily scrum
meeting is held, and a
sprint review was written
after each sprint.
Lastly, for the closing
phase, in prescriptive
approach, a lesson
learned report is written
whereas in agile
approach, a sprint
retrospective is written
which is intended to
answer
two fundamental
questions; What went
well during the last sprint
that we should continue
doing and what could we
do differently to improve
the product or process?
Although both
approaches do differ a
lot, the main difference
that we found was the
iterations. With the agile
approach, since they
were able to deliver
multiple versions, they
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
- Access to all documents
- Unlimited textbook solutions
- 24/7 expert homework help
could accept feedback
and work on it before
releasing the second
update. With
prescriptive or waterfall
approach, there was only
one final product and
there was no
chance of re-doing or
changing the product
after the release.
2. When should you use a
more prescriptive or agile
approach?
Projects with heavy
constraints,
inexperienced and
dispersed teams, large
risks, generally
clear up-front
requirements, and a fairly
rigid completion date are
best done using a
predictive approach.
In contrast, projects with
less rigid constraints,
experienced and
preferably co-located
teams, smaller risks,
unclear requirements,
and more flexible
scheduling would be
more
compatible with an agile
approach.
What are the main
differences between the
two versions of the JWD
Consulting case
study?
The differences are as
follow:
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
- Access to all documents
- Unlimited textbook solutions
- 24/7 expert homework help
Firstly, the main
difference between pre-
initiation would be
determining roles and
deciding what
functionality would be
delivered as part of each
release, how many
sprints
will be required to
complete a release, and
how many releases of
software to deliver. In
the prescriptive
approach, only one
release of the software
would be made which will
be
at the very end.
Secondly, in prescriptive
approach the planning
process includes creating
a team charter,
WBS, Gantt chart, and list
of prioritized risks for the
whole project. In agile
approach, the
team follows a scrum
method; a preliminary
scope statement is
written and in place of a
WBS, high-level
descriptions of the work
to be completed would
be identified in the
product and sprint
backlogs.
Thirdly, the team would
complete tasks each day
in both approaches, but
by using an
agile approach, the team
would produce several
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
- Access to all documents
- Unlimited textbook solutions
- 24/7 expert homework help
iterations of a potentially
shippable
product.
Next, in the prescriptive
approach, a brief
progress report was
submitted each Friday.
However, in agile
approach, daily scrum
meeting is held, and a
sprint review was written
after each sprint.
Lastly, for the closing
phase, in prescriptive
approach, a lesson
learned report is written
whereas in agile
approach, a sprint
retrospective is written
which is intended to
answer
two fundamental
questions; What went
well during the last sprint
that we should continue
doing and what could we
do differently to improve
the product or process?
Although both
approaches do differ a
lot, the main difference
that we found was the
iterations. With the agile
approach, since they
were able to deliver
multiple versions, they
could accept feedback
and work on it before
releasing the second
update. With
prescriptive or waterfall
approach, there was only
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
- Access to all documents
- Unlimited textbook solutions
- 24/7 expert homework help
one final product and
there was no
chance of re-doing or
changing the product
after the release.
2. When should you use a
more prescriptive or agile
approach?
Projects with heavy
constraints,
inexperienced and
dispersed teams, large
risks, generally
clear up-front
requirements, and a fairly
rigid completion date are
best done using a
predictive approach.
In contrast, projects with
less rigid constraints,
experienced and
preferably co-located
teams, smaller risks,
unclear requirements,
and more flexible
scheduling would be
more
compatible with an agile
approach.
In the JWD consulting project there were five key differences between the two versions
of the case. First, in the agile approach multiple releases would occur, in the perspective
approach the software would be released only a single time which would be mark the
completion of the project. A second difference is that in the perspective approach a team
charter, WBS, Gantt char and a list of prioritized risks for the entirety of the project is part of the
planning process. However, in the agile approach a scrum method is used instead. A third
difference is that using the agile approach the team would produce multiple versions of the
software leading up to a launch. Fourth, using the agile approach daily meetings were held
whereas in the perspective approach a brief progress note was sent at the end of each week.
Overall the difference between the agile and perspective versions of the project was that
the agile approach delivered multiple options and therefore could accept feedback and make
adjustments as the project continued to develop. The perspective approach wielded one final
product that could accept feedback, but not do anything to make changes or corrections. In the
perspective approach it was more well suited because it had a clear budget and timeline with a
well-defined focus and more intensive research could be done that allowed for a fuller
understanding of the product. However that approach is not at all flexible and there is little
room for error. In the agile approach the risks are lower and the overall project has more
flexibility as updates can be made after each version release which gives JWD more control over
the project as a whole. These factors produce a higher level of customer satisfaction in general
because the product has received feedback. The downside to the agile approach is that the
project can in theory go on forever and costs continue to rise and often exceed budget due to
constant changes and updates pushing timelines to ROI further back. After reading both
versions it appears JWD users would prefer an agile approach. The technological world is every
changing and therefore the ability to make updates and changes as needed would be beneficial
Additionally if the initial launch garnishes a lot of negative feedback there is plenty of room to
make changes and improvements. The company would also be able to have the product live
sooner as they could launch a rudimentary version and then take user feedback and apply it to
the next version release.
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
- Access to all documents
- Unlimited textbook solutions
- 24/7 expert homework help