ITECH7401 Leadership In IT Project Management



The business case is the first deliverable during an IT project’s life cycle.

It provides an assessment of the organisational potential, feasibility, costs and benefits of various alternatives or options.

A business case can help you determine whether an investment in a project is justified.

The business case describes the problem and its consequences and provides a cost benefit analysis.

The business case may also examine alternative solutions.

A business case should be used to verify that the project is aligned with the organisation’s strategy plan.


You will need to form four (4) team members for this assignment.

The project leader will be chosen by one team member for the duration.

The project business case will be prepared by the teams based upon an IT project case study. Teams should make their own assumptions and schedule all deliverables.

A digital copy of the case study can be obtained from your tutor or lecturer. Alternatively, your team may want to propose their own project. Before proceeding, please get permission from your lecturer.

Idealerweise, the business case should include details about the following:

Description and introduction to the background of the project

Description of project objectives (including link with organisational mission statements)

Description of the current state (including a SWOT analysis).

Summary of problem/opportunity statement

Details about critical assumptions and constraints

Analyse of options and possible recommendations

Financial analysis (npv/roi, payback figures and financial analysis)

Preliminary requirements for the project (project preliminary scope).

Budget estimation (cost model and baseline).

Schedule estimate (including work breakdown level 3)

List of potential risks


Summary of the Case

To develop an app that allows for future scaling; to complete the application within the given time and budget using all available resources.

It is possible that the project will undergo many changes. This should be taken into consideration when creating a development program.


Jack Bartlett: CEO heartland, representing Heartland. Client

Peter Morris, CEO of Equine: Development Company

Lisa Stillman, Equine Director Mobile Development

Author: Project manager

Mallory Wells, Heartland liaison, representing Heartland

Development team: 2 programmers (and

Digital image specialist

Time and Budget

Period: 20 weeks

Not required

App that works on both Android and Iphone platforms

Proposed Development Approach

Looking at the requirements and the deliverables, the proposal calls for an agile development approach. It will use the SCRUM method of development.

SCRUM will be the development platform. It is based on the principles and practices of project management for software projects (‘Scrum Alliance 2017).

SCRUM is an Agile development method. It’s a lightweight operation framework that allows agile software development.

A “process frame” is a collection of activities and practices that are required to ensure that the process conforms with the framework.

This flexible and holistic process of development allows for minimum product shippable. Software is developed in short bursts, tested and captured customer views. Finally, additional programming or incremental programming is completed until the final product is produced (Bhala (2015)).

This method has the advantage that errors can be eliminated or reduced significantly, as any issues and errors are addressed in the early stages of the development.

It helps manage risks like not meeting client needs. Frequent iterations are created and tested. Client input is taken into consideration as well as any new requirements. These will be incorporated into the development.

The development process will begin with a meeting of the client to determine their needs and then meet all the stakeholders to define the terms.

Next, Ty,Wells and the Equine Team of the project manager and programmers will be present. The image specialist will also attend.

Ty and Wells will serve as users during this meeting. This will allow them to visualise and communicate the exact needs and wants of the customers who will be using the games.

The meeting will produce the user documentation (initial), which will then be used for development using the SCRUM framework by Deuff, & Cosquer (2013), (Pries & Quickley (2011)).

The Development Team (The Scrum Team).




Mallory Wells to represent Heartland

Product Owner

Author Add Name

Programmer (coder)

Image specialist

Planning: Work Flow

The planning phase takes two days. Here the scrum team will hold meetings to discuss roles and activities as well the sprint planning event.

For the development of the application, there will be five sprints lasting four weeks.

The scope of the work will be communicated during the scrum meeting. This is based on the user requirements document (Rubin 2013, 2013).

The product backlog items are created to determine the tasks to be completed and the activities to be carried out for each scrum.

Agile software development is a process that produces final software at the end. This will happen over five sprints.

Each sprint meeting is where the scrum team meets to discuss the tasks that must be completed within the given sprint. They also assign roles and specify the requirements and accept criteria (Maximini 2015).

Once the detailed tasks have been defined, the team will then work on the items in the backlog that were selected for the confirmed sprint backlog.

In addition to identifying the locations of the daily backlogs, the meeting will also discuss the rules of engagement for the daily scrums.

Product Backlog

Interpreting user requirements (Heartland & future customers).

Definition of the programming languages that will be used and their justification

The game features are what the game allows users to do.

Definition of the requirements for playing the game (hardware/software for the phone).

Production of the first MSP

Ty Borden tested the MSP, and received feedback

Refinement and source of graphic materials

For each aspect of the game, generate cheats

Test the game components together

Multi-platform testing and extensive testing

Develop the servers and platforms to download the game


Sprint Retrospective meeting

User Stories

To create the software, user stories must first be created. They help to clarify the tasks and reduce the sprint backlog. The user stories are based upon the user requirements document, planning meeting and input from the product owner (‘Agile modeling’, 2017).

User Story 1

I would like to try the application as a customer. I can download it from either the Icloud/Appstore or Google Playstore. I don’t have to make any payments, nor do I need to give my credit card details.

This is done to make sure that the game is enjoyable before I decide to purchase the full product.

The trial period should not exceed 14 days. After that, neither party can make any commitment.

User Story 2

I am a user and want to download the app but not use any data bundles. The application must not take up more than 100MB of my mobile device’s disk space after installation.

User story 3

It should work with older versions of my operating system on my mobile device. IOS Version 5 for Apple Devices and Android 4.0 For Android Devices. The application should not cause my device to freeze or hang while I play the game. Background functions, such as web connections, should continue.

User story 4

I should be capable of downloading and playing the full version. The game should not drain the battery too quickly; on average, a full game should take four hours to drain the battery.

User story 5

As a user, I expect cheat features. Also, the game should go from the lowest difficulty level to the highest.

User story 6

As a user, the game should allow me to pause it and put it in the background. I will also be able view mails, pick up a phone, and reply to a message.

User story 7

You, the user, shouldn’t be able to install malware or other advertisements on the game. I should also have the option to turn off/on these ads in the game settings.

You should also be able to customize your preferences and settings in the settings section.

User story 8

As Heartland, you should have administrator privileges. This will allow you to log into the AppStore and Google Play consoles to view the number and payment history of the respective applications.

User story 9

I, the product owner, should be able seamlessly to get updates and newer versions created and integrated into the Applications Store (AP Store of Google Play); this should elicit a notification from the customer to install the latest version.

User Story 10

The application should contain a simplified end-user license agreement for consumers. This agreement should be concise, simple, and clear to clearly define the terms.

User story 11

A game that is easy to learn and fun for users should have high-quality graphics.


Each sprint begins with a sprint planning session where deliverables will be defined and roles assigned.

Sprints will have daily scrum meetings, where tasks for each day will be set and reviewed. Scrum master and product owner will then chair these meetings and encourage contributions from the whole scrum team.

Every sprint will end with the application being tested. The first test will be done by the internal team. The product owner will then be the lead tester, and the team will provide feedback.

Once satisfied, the product owners will approve and accept iterations based upon the agreed acceptance criteria (Ricardo 2013).

Based on the user stories, acceptance criteria will apply. Testing will take place internally (by teams) every Friday. Customer input will also be sought at the end of each sprint. Documentation will be required for any additional requirements.

The sprint review meeting will see the MSP delivered to the customer. There will be a sprint retrospective meeting where the sprint is reviewed, and plans for the next sprint are made (‘Software testing help’, 2017.

Below is an illustration of the development process for the application.

Risk management is the management of risks through the identification, development, and review of mitigation approaches. The Scrum master is responsible overall for risk management (Yegi (2014)).


Members of the team create code that does not comply with user stories

The product owner can review functionality and approve/disapprove the code

The downloaded file is greater than the 100 MB limit.

For a light-weight app, you can use languages and cut out all the components such as images and video

Exceeding budget and time

Plan effectively and continually refine functions

Some user stories have not been fully addressed

Do sprint reviews. Refine any issues before moving to the next stage.


Agile Management for Software Engineering (1st Ed.).

R. Bhala (2015), April 29.

Better Sprint Planning.

User-centered agile methodology (1st Ed.).

Essential Scrum is a practical guide to one of the most popular agile processes.

Upper Saddle River NJ: Addison-Wesley.

The Scrum culture is about introducing agile methods into organizations.

Extreme programming and software engineering: agile processes

What is Scrum?

Scrum Alliance is an Agile Framework for Complex Projects.

Software Testing Help

Getting Started with Agile Scrum Methodology – The Complete Guide for Software Developers & Testers — Software Testing Support.

Scrum Process Issue and Risk Management

Leave a Reply

Your email address will not be published.