ITECH7401 Leadership In IT Project Management

Table of Contents



The first deliverable of the IT project lifecycle is the business case.

This provides an analysis of organisational value, feasibility costs, benefits and risks for several alternatives.

The business case is used to assess whether a project is worth the investment of an organisation.

The business case identifies the problem and the impact, and then calculates the cost-benefit analysis for the proposed solution.

The business case also considers possible alternatives.

It should also include a review of the business case to ensure that the project is in line with the organization’s strategic plan.


This assignment will require you to form four (4) teams.

For the duration of this project, one member of each team will be elected project leader.

Each team will create a project business plan based on an IT case study. They should take responsibility for scheduling and assumptions.

You can request an electronic copy of the case study from your tutor/course lecturer. Alternatively, your team might wish to submit their own project. Please get permission from your lecturer before proceeding.

The business case should include the following details:

Introduction and description of the project background

Description of the project objectives (with link to the organisational mission statement).

Description of the current situation (including SWOT analysis).

Description of the problem/opportunity statement

Details of the critical assumptions and constraints

An analysis of the options and recommendations

Financial analysis (npv and roi)

Preliminary project requirements (project preliminary scope).

Budget estimate (cost model, baseline)

Schedule estimate (including work breakdown structure level 3).

List of possible risks


Summary of the Case

To create an application that can be scaled in the future. To complete the project within the time and budget given, while maximizing the resources.

When developing a development plan, it is likely that there will be many changes.


Jack Bartlett, CEO, Heartland, representing Heartland: Client

Peter Morris, Equine: Development Company CEO

Lisa Stillman; Equine director Mobile Development

Author: Project manager

Mallory Wells: Heartland liaison representing Heartland

Development team: Two programmers (and )

Digital image specialist

Time and Budget

Period: 20 Weeks


A mobile app that can be used on both the Iphone and Android platforms

Proposed Development Approach

The requirements and deliverables are being considered. This proposal proposes an agile development approach using the SCRUM development methodology.

SCRUM will serve as the development platform and follow the principles of project management (‘Scrum Alliance’ 2017, 2017).

SCRUM, a form Agile development, is widely used. It is a light operation framework for agile software programming.

A “process framework” is a set of specific practices and activities that must be followed in order to ensure the process follows the framework.

This is a flexible, holistic development process that produces minimum viable products. It involves short sprints of software development. Customers are surveyed and feedback is taken. Then, incremental programming is done until the final product is created (Bhala 2015).

Because errors and problems are addressed at the beginning of development, this has the advantage of reducing or eliminating them completely.

This helps to manage risks such as missing client requirements. Iterations are frequently developed and tested with clients’ input. Any new requirements or modifications that might be overlooked are taken into account and incorporated into the next development.

The client will meet with the team to discuss their requirements. They will also meet with all stakeholders to agree on the terms.

The Heartland staff, Ty Wells, the Equine team manager, programmers, as well as the image specialist, will meet again to discuss the terms.

Ty and Wells will act as users in this meeting to visualize and communicate exact requirements of customers who will be playing the games. The user requirement are both functional (ability of both Android and IOS platforms to work seamlessly) and non-functional. They must be simple to use and intuitive so that users can quickly learn the game and don’t take up too much space on the mobile device.

This meeting will create the initial user documentation, which will be used to develop the SCRUM framework (Deuff & Cosquer 2013, (Pries & Quintley, 2011).

The Development Team (The Scrum Team).




Mallory Wells will represent Heartland

Product Owner

Author Add Name

Programmer (coder for the game).

Image specialist

Planning: Work Flow

The planning phase will last two days. This is where the scrum team will meet to discuss roles, tasks and activities, as well as the sprint planning event.

Five sprints, each lasting four weeks, are planned for the development and maintenance of the application.

The scope of work is discussed during the scrum meeting according to the deliverables and user requirements (Rubin, 2013).

To determine the tasks and activities that will be performed for each scrum, product backlog items must be created.

The final software will be available at the end, which is an agile process. It will be ready after five sprints.

The scrum team meets for each sprint to discuss the tasks and assign roles.

These tasks will be used to complete the sprint backlog items.

This meeting will also identify the locations where the daily backlogs are to be kept and the rues for engagement for daily scrums.

Backlog of Product

Interpreting the requirements of the user (Heartland, future customers)

Definition and justification of programming languages to use

The game features: defining the capabilities of the game and what it will allow users to do.

Determining the requirements to play the game (hardware, software, and the phone)

The first MSP was produced

Ty Borden tested the MSP and received feedback

Refinement and sources of graphics

Each aspect of the game can be cheated by creating cheats

Testing the game components by combining them

Large scale testing of different platforms and devices

Development of the platforms and servers for the game’s download


Sprint Retrospective Meeting

User Stories

The user stories are essential for the development of the software. These help to refine the teaks and sprint backlog. User stories are based on the user requirements document and planning meeting with input from product owners (‘Agile Modelling’, 2017).

User Story 1

I am a customer and would like to be able to download the application from the Icloud / Apple Appstore, or Google Playstore. I will then be able to test the application before I commit to any purchases or make any commitments.

It is important that I feel satisfied with the game before making a purchase or downloading the full product.

The trial period should last at most 14 days. Neither party is required to purchase the full product after that time.

User Story 2

I, as a user, want to download the game and use minimal data bundles. After installation, the application shouldn’t occupy more that 100 MB of mobile device disk space. It should only work on a mobile device with at least 1 GB RAM.

User story 3

The app should work with older operating systems on my mobile device. IOS version 5 and Android 4.0 are available for Apple devices. While playing the game, my device should be frozen or hanged. Background functions like web connections should also be allowed to continue.

User story 4

I should be able download the full version and it should not drain my battery too much. A full game should only drain your battery after four hours of continuous gaming on average.

User story 5

I, the user, should have cheat features. The game should move from low difficulty to high difficulty.

User story 6

As a user, I can pause the game to attend to other phone issues such as answering a call or viewing mails. Then, I can return to the game to continue playing from the previous instance.

User story 7

As a user, the game should not contain malware or advertisements. If there are ads, I should have the ability to disable them in the game settings.

A settings section should be available in the game so that I can customize my preferences and settings.

User story 8

As Heartland, my administrator privileges should allow me to log in to the AppStore or Google Play consoles. I will be able to see the number of times an application has been downloaded as well as review the payments made with each application store.

User story 9

I, the product owner, should be able seamlessly to update and incorporate newer versions into the apps store (AP Store on Google Play); this should prompt a notification to the customer to download the latest version of the application at no additional cost.

User Story 10

To be understood by the consumer, the application must contain a simple end-user license agreement. It should be short and concise to clarify the terms.

User story 11

The game should be easy to use and have great graphics.


The sprint process begins with a sprint planning meeting, where deliverables and roles are assigned.

Daily scrum meetings will be required for sprints. These meetings will set the tasks and assign roles. The previous day’s tasks will also be reviewed. Product owner and scrum master will lead the meetings and invite contributions from all members of the scrum team.

The application will be reviewed and tested at the end of each sprint by both the internal team and the product owner. They will also have feedback from the entire team.

The product owner will approve and then accept the iteration based on the accepted criteria (Ricardo 2013, 2013).

Based on user stories, the acceptance criteria will be established. The sprint will include internal testing (by team), and customer testing at the end. All input will be obtained from the customer and any new requirements documented.

Sprint review meetings will include delivering the MSP directly to the customer. This is followed by a sprint retrospective meeting, in which the sprint is reviewed.

Below is a visual representation of how the application will be developed.

Risk management: managing risks by identifying and developing mitigation strategies, reviewing, and the Scrum master is responsible for overall risk management (Yegi 2014).


Code that doesn’t meet user stories is developed by team members

Product owner must review the functionality and approve/disapprove code

When downloaded and installed, the application is larger than the limit of 100 MB

To create a lightweight application, use languages and remove all components (images and video).

Budget and time were exceeded

Effectively plan continuously and refine your functions

Some user stories may not be fully fulfilled

Before moving on to the next step, conduct sprint reviews.

Refer to

Agile Management for Software Engineering (First ed.

R. Bhala (2015, 29 April).

Better Sprint Planning.

The user-centered agile method (1st edition).

Essential Scrum: A practical guide to the most widely used agile process.

Upper Saddle River (NJ): Addison-Wesley.

The Scrum culture: Implementing agile methods in organizations.

Software engineering and extreme programming: Agile methods

What is Scrum?

Scrum Alliance – An Agile Framework to Complete Complex Projects.

Software testing assistance

Getting Started With Agile Scrum Methodology — The Complete Guide For Software Developers And Testers — Software Testing Assistance.

Scrum Process Risk and Issue Management.

How do you place an order?

It takes a few steps to place an order with Us:

  • The first step is to place your order. You will need to provide us with some basic information about your project.
  • Once you have placed your order, you will be taken to our secure payment page.
  • Once we receive your order, we will carefully review it and match you with a writer who has the skills and experience.
  • Stay in contact with the writer and discuss vital details of research.
  • Your completed proposal will be delivered via email within the specified deadline.

You are secure when using our service

It's critical for each client to feel secure. As a result, we at Research Proposal Writing take precautions to secure your data.

Financial security You may securely pay for your purchase using a variety of secure payment methods.
Personal security The personal information of our clients is secure. Nobody else will have access to it.
Academic security We use a specialized program to check every completed paper to ensure that we deliver no-plagiarism samples.
Web security This website is safe from unauthorized breaches. We maintain our privacy management in line with the latest laws and regulations.

You can get help placing your order. If you have any questions about our services, please contact us. Our support staff is accessible 24 hours a day, 7 days a week.

If you're still looking for a way to improve your grades and hire expert writers, we've got you covered. Place an order on our website, and we'll help you with any paperwork you want. We will exceed your expectations.

Order now Get a quote