Please note that this mini$-$case is designed to help you think about IS project management and new systems design and implementation. The primary outcome of this discussion is to sensitize you to the need to have a productive partnership between business stakeholders and IS professionals during new systems development. While the case is perhaps a bit unrealistic, with the protagonist making some grave mistakes $($hints$),$ the incident described here clearly suggests that the blend of skills needed for new systems design, development and implementation are rarely found in one person or one function, thus leading to misunderstandings and confusion.

The goal of this case $($as in previous cases$)$ is not to provide right or wrong answers, but to raise issues.

What would you do differently, if anything, given the chance to start this project all over again?

To answer this question, review information on the System Development Life Cycle $($SDLC$)-$ in the summary notes or course textbook. Specifically understand the goals of SDLC $($e$.$g$.$ what can the protagonist do differently if they were aware of the concepts in SDLC$?).$ What is your understanding of scope creep, and does it apply in this case? If yes, how did it develop and how can it be eliminated or minimized? What are the pros and cons of user involvement?

In your responses, answer how or what you would do differently and give a deep dive into the reasoning behind your answers.

What should your agenda for tomorrow$$s meeting be$?$ Should you press on with your strategy, or is it a change of course in order?

There is a lot to be discussed but include the main ideas such as the difficulties associated with de$-$escalation of ongoing projects. Provide justification for the chosen items.