Itech7401 Leadership In It: Scrum Assessment Answers
Assessment Details
Background
A business case is the first deliverable in the IT project life cycle. It provides an analysis of the organisational value, feasibility, costs, benefits, and risks of several proposed alternatives or options.
A business case helps to determine whether or not a project justifies an organisations investment into a project. The business case defines the problem and its impact and performs a cost benefit analysis for the proposed solution. It also looks at possible alternative solutions. The business case should also provide a check to see that the project aligns with the organisation’s strategic plan.
For on preparing a business case, see: http://www.cio.com.au/article/433382/how_make_winning_business_case/
Requirements
In this assignment, you will be required to form teams of approximately four (4) people. One team member is to be elected the project leader for the duration of the project. Teams will prepare a project business case based on an IT project case study and should use their own initiative regarding assumptions and the scheduling all deliverables.
An electronic copy of a case study will be available from your tutor or course lecturer (alternatively your team may wish to propose their own project—please get permission from your lecturer before proceeding with this).
Ideally the business case should contain details of the following:
- introduction and description of project background
- description of project objectives (including link to organisational mission statement)
- description of the current situation (including a SWOT analysis)
- outline of problem/opportunity statement
- details of critical assumptions and constraints
- an analysis of options and recommendations
- financial analysis (npv, roi and payback figures)
- preliminary project requirements (project preliminary scope)
- budget estimate (cost model and baseline)
- schedule estimate (including work breakdown structure level 3)
- list of potential risks
Answer:
Case Summary
To develop an application with features for scalability in future; to develop the application within the specified time and budget, using the available resources. There is likely to be several changes while undertaking the project and this must be considered when coming up with a development plan.
Stakeholders
- Jack Bartlett: CEO, heartland, representing Heartland : Client
- Peter Morris, CEO Equine: Development Company
- Lisa Stillman; Equine Director Mobile Development
- Author: project manager
- Ty Borden: Sponsor: Internal IT liaison
- Mallory Wells : Heartland liaison, representing Heartland
- Development team: Two programmers ( and )
- Digital image specialist
Budget and Time
$260000
Contingency (10%); $26000
Period: 20 weeks
Required
An App for use in both Iphone and Android platforms
Proposed Development Approach
Looking at the deliverables and the requirements, the proposal is to have an agile development approach, specifically using the SCRUM methodology for development. The SCRUM methodology will be the development platform, and run using the principles of project management for software projects (‘Scrum Alliance,’ 2017). SCRUM is a form of Agile development and is a lightweight operation framework for agile software development, which is used widely. A “process framework” refers to a specific set of practices and activities that have to be followed to ensure the process is consistent with the said framework. It is a flexible and ‘holistic’ process of development in which minimum shippable products of the software is developed in short bursts (sprints) and tested, customer views captured, and improvements made, then additional/ incremental programming done , until the final product is developed (Bhala, 2015). This has the advantage of eliminating errors or reducing them significantly because any problems and errors are dealt with at the initial stages of the development. It also helps in managing risks, such as not meeting client requirements because frequent iterations are developed and tested, with the clients’ input and any new requirements that may have bee overlooked taken into consideration and incorporated in the subsequent development.
The development will start with a meeting with the client to establish their needs by meeting with all the stakeholders to set the terms. A subsequent meeting will involve the Heartland staff, Ty,Wells, and the Equine team of the project manager, the programmers, and the image specialist. In this meeting, Ty and Wells will also act as users to visualize and communicate the exact needs of the customers that will be playing the games; the user requirement are both functional (ability to work seamlessly in both Android and IOS platforms) without errors, and non-functional; be easy to use and have an intuitive way so users can learn the game quickly and not take up too many resources of the mobile device, while not causing errors. The meeting will develop the user documentation (initial), that will then be used as the bass for the development using the SCRUM framework (Deuff, & Cosquer, 2013), (Pries & Quigley, 2011).
The development Team (The Scrum team)
|
Function |
Person |
|
Client |
Mallory Wells to represent Heartland |
|
Product Owner |
Author {Add Name} |
|
Programmer (coder of the game) |
{Add Name} |
|
Programmer (multi platform functionality) |
{Add Name} |
|
Image specialist |
{Add Name} |
|
Scrum master |
Ty Borden |
Work Flow: Planning
The planning phase will take two days where the scrum team will hold a meeting to discuss roles, activities and tasks, and the sprint planning event. The project envisages having five sprints of four weeks each for the development of the application. During the scrum meeting, the scope of the work to be done is communicated, according to the user requirements document and deliverables (Rubin, 2013. The product backlog items are then developed to define the tasks to be done and what activities will be done for each scrum. Being an agile process, the final software will be ready at the end of the project period, consisting of five sprints. For each sprint meeting, the scrum team meets and discusses the tasks to be completed within the specified sprint and assigns roles; the requirements are specified and the acceptance criteria for the sprint (Maximini, 2015). The detailed work tasks are then defined that are necessary for completing the backlog items that have been selected to create the confirmed sprint backlog. The meeting will also specify the locations for having the daily backlogs and the rues of engagement for the daily scrums
Product backlog
|
Planning meeting |
|
Interpreting the user requirements (Heartland and future customers) |
|
Definition of the programming languages to be used and their justification |
|
The game features; defining what the application game will enable users to do and what cannot be done |
|
Defining requirements for playing the game (hardware and software for the phone |
|
Producing the first MSP |
|
Testing the MSP with Ty Borden and obtaining feedback |
|
Graphics sources and refining |
|
Generating cheats for the game for each aspect of the game |
|
Combining the game components for testing |
|
Wide scale testing on different devices and platforms |
|
Developing the servers and platforms for downloading the game |
|
Documentation |
|
Sprint Retrospective meeting |
|
Product delivery |
User Stories
To develop the software, the user stories must be developed; these help refine the teaks to be done and the sprint backlog; the user stories are developed based on the user requirements document, planning meeting, with input from team members and the product owner ('Agile Modeling', 2017).
|
User Story 1 |
As a customer, I want to download the application from either the Icloud / Apple Appstore or Google Playstore and download a trial version of the application without making any payments or making commitments, by way of giving credit card details. The aim is to be sure I like the game before thinking of making a full purchase/ downloading the full product. The trial period should be at least 14 days, during which neither party has any obligation |
|
User Story 2 |
As a user, I want to download the game but use minimal data bundles; after installation, the application should not occupy more than 100 MB of the mobile device disk space and should work with a mobile device with 1 GB or mobile device RAM |
|
User story 3 |
The application should work even with older versions of the operating systems in my mobile device; IOS version 5 for Apple devices and Android 4.0 for Android Devices and while playing the game, it should freeze my device or cause hanging, and allow background functions such as web connections to go on |
|
User story 4 |
I should be able to download and play the full version, and the game should not drain my device battery too much; a full game should drain the battery after four hours of constant gaming, on average |
|
User story 5 |
As a user, I should have some cheat features and the game should progress form low levels of difficulty to the highest difficulty levels |
|
User story 6 |
While playing the game, as a user, I should be able to pause the game and relegate it to the background and attending to other phone issues, such as picking a call, replying to a message, or view some mails and go back to the game and continue playing it from the last instance |
|
User story 7 |
The game, as a user, should not come with malware or any advertisements, and in case there are adverts, then I should be given the option to enable/ disable these functions in the game settings. The game should also have a settings section where I can choose my preferences and settings |
|
User story 8 |
As Heartland, I should have administrator privileges where I can log in to the AppStore and Google Play consoles and know the number of times the application has been downloaded and review payments with the respective application stores |
|
User story 9 |
As the product owner, I should be able to have updates and newer versions developed and incorporated into the applications store (AP Store of Google play) seamlessly; this should elicit a notification to the customer do download the newer venison of the application, at no extra cost |
|
User Story 10 |
As a consumer, the application should have a simplified end user license agreement that is simple, short,and concise, to define the terms of agreement |
|
User story 11 |
As a user, the game should have rich graphics, and yet be simple enough to learn and play, with a brief demo of the game and how it works |
Development
For each sprint, the sprint process starts with a sprint planning meeting where deliverables are defined and roles assigned. The sprints will require daily scrum meetings where the tasks to be undertaken for the day are set and defined and whose role it will be, and then previous day’s tasks are reviewed; the product owner and scrum master will chair the meetings and solicit contributions from the entire scrum team. At the end of every sprint, the application will be tested; first by the internal team; the product owner will be the lead tester and will have the team present to get feedback. If satisfied, the product owner will then approve and accept the iteration, based on the set acceptance criteria (Ricardo, 2013). The acceptance criteria will be based on the user stories; testing will be done internally (by team) every Friday, and the testing at the end of the sprint done with the customer, and their input obtained, as well as any new user requirements documented. The sprint review meeting will entail delivering the MSP to the customer; this is to be followed by a sprint retrospective meeting in which the sprint is reviewed and planning done for the next sprint ('Software testing Help', 2017). Below s a visual framework of how the application is to be developed;
Risk management: risks to be managed by identifying, developing approaches for mitigation, and reviewing; the Scrum master responsible for overall risk management (Yegi, 2014)
|
Risk |
Mitigation |
|
Team members develop code that does not meet user stories |
The product owner to review functionality and approve or disprove code |
|
The application is too big than the set limit of 100 MB when downloaded and installed |
Use languages and strip don components including images and video to have a light-weight application |
|
Time and budget exceeded |
Plan effectively continuously and refine functions |
|
Some user stories are not fully met |
Have intensive sprint reviews and refine any issues before going to the next step |
References
Anderson. (2004). Agile Management for Software Engineering (1st ed.). Delhi: Pearson India.
Bhala, R. (2015, April 29). Better Sprint Planning. Retrieved May 14, 2017, from https://www.scrumalliance.org/community/articles/2015/april/better-sprint-planning
Deuff, D., & Cosquer, M. (2013). User-centered agile method (1st ed.). Hoboken, NJ: Wiley.
Rubin, K. S. (2013). Essential Scrum: a practical guide to the most popular agile process. Upper Saddle River, NJ: Addison-Wesley.
Maximini, D. (2015). The Scrum culture: introducing agile methods in organizations. Cham: Springer.
Pries, K. H., & Quigley, J. M. (2011). Scrum project management. Boca Raton, FL: CRC Press.
Ricardo, C. (2013). Agile processes in software engineering and extreme programming. Heidelberg: Springer-Verlag Berlin An.
'Scrum Alliance'. (2017). What is Scrum? An Agile Framework for Completing Complex Projects - Scrum Alliance. Scrumalliance.org. Retrieved 14 May 2017, from https://www.scrumalliance.org/why-scrum
'Software testing Help'. (2017). Getting Started with Agile Scrum Methodology: The Complete Guide for Software Developers and Testers — Software Testing Help. Softwaretestinghelp.com. Retrieved 14 May 2017, from https://www.softwaretestinghelp.com/agile-scrum-methodology-for-development-and-testing/
Yegi, S. (2014). Risk and Issue Management in the Scrum Process. Scrum Alliance. Retrieved 14 May 2017, from https://www.scrumalliance.org/community/articles/2014/april/risk-and-issue-management-in-scrum-process
Buy Itech7401 Leadership In It: Scrum Assessment Answers Online
Talk to our expert to get the help with Itech7401 Leadership In It: Scrum Assessment Answers to complete your assessment on time and boost your grades now
The main aim/motive of the management assignment help services is to get connect with a greater number of students, and effectively help, and support them in getting completing their assignments the students also get find this a wonderful opportunity where they could effectively learn more about their topics, as the experts also have the best team members with them in which all the members effectively support each other to get complete their diploma assignments. They complete the assessments of the students in an appropriate manner and deliver them back to the students before the due date of the assignment so that the students could timely submit this, and can score higher marks. The experts of the assignment help services at urgenthomework.com are so much skilled, capable, talented, and experienced in their field of programming homework help writing assignments, so, for this, they can effectively write the best economics assignment help services.
