Reference no: EM132415041

ITECH 7415 Masters Project - Federation University

PROJECT

DETAILS OF IT PROJECT:

PROJECT - Blockchain Credits for collaborative ventures

Many apps are developed by teams of enthusiasts who cooperate to develop code at their own expense. The client firm brings together such teams, and whilst the resulting apps may be made available free via the internet, the client firm has experimented with a reward system for contributors based on both their contributions, recorded as transactions, and user uptake of the app.

Current practice draws on a form of reward token called STEEM. However some STEEM users have reported difficulties in the way it is organised. The project task is to document the as-Is situation and identify potential problems, then propose a to-be situation that compares the continuing use of STEEM with other emerging reward systems.

Assessment Task 1 - Project Storyboard

The purpose of the Project storyboard is to:
• Outline the project problems and objectives
• Clarify Client's expectations
• Provide an opportunity for students to demonstrate understanding of the project
• Encourage students to discuss initial ideas to address project problems.
• Outline the Client's preferred way of working with the students, recognising that some clients may not be readily available for face-to-face meetings when needed to fit in with scheduled student activities.
• Start with a broad outline and a few key ‘user stories', then have students expand the list of user stories in conjunction with the client and outline some solution concepts for client review

Masters Project

The Weekly Stand-Up is a weekly project update delivered by every student as part of Project discussions. Each student is expected to provide a 3-minute update on the status of the project and allocated tasks, by answering the following questions:
i) What did you accomplish since the last meeting?
ii) What are you working on until the next meeting?
iii) What is getting in your way or keeping you from doing your job?

This task will be assessed by the lecturer using the following criteria:
i) Completion of allocated tasks in accordance with Product Roadmap
ii) Understanding of individual contribution to the Product(s).
iii) Evidence of participation and collaboration

Assessment Task 2

Product Roadmap

The product roadmap is a high-level view of the product requirements needed to achieve the product vision. A product roadmap is a document that outlines the goals, milestones, and deliverables for a product in development.
The product Roadmap enables a project team to outline a general timeframe for when you will develop and release those requirements. The product roadmap is a first cut and high-level view of the product backlog and reflect the product to be developed in order to address the user stories.Roadmaps are essential for coordinating the product development process. They ensure that ongoing day-to-day tasks align with and contribute to business strategy.

The Product Roadmap should include:

The Product Vision: The product vision statement is an elevator pitch, or a quick summary, to communicate how your product supports/addressesyour client's goals. The vision statement must articulate the goals for the product.

Product Backlog: The full list of what is in the scope for your project, ordered by priority. After you have your first requirement, you have a product backlog.

Revised User Stories: a clear identification of the project requirements and objectives. Acceptance criteria for user stories should also be included.
Product Schedule: goals, milestones, and deliverables for a product in development.

Sprint Retrospective

Each studentis expected to submit a retrospective at the end of each sprint. The retrospective should be a video recording (no more than 5 minutes) embedded as a media file in the portfolio. Students are welcome to attach documents to support retrospectives.
Reflections are expected to cover both team and individual components of the project:

(a) Team Component

This is a summary of what happened in a Sprint. For example:
•The date the Sprint started and the date it ended
•Who was in the team (including how many days each person worked)
•Which user stories were in the Sprint Backlog (including their estimate and whether they were completed by the end of the Sprint)
•Evidence of work done in the Sprint

(b) Individual Component

Individual component should include personal tasks and learning during the Sprint and should provide answers to the following questions:
•What did I accomplish in the past sprint?
•How did I apply stream specific knowledge to my project?
•What did I learn from in the past sprint?
•What could have gone better in the sprint?

Project Write-Up

The Project Write-Up highlights the conclusion of the project's work. The objective of this document is to provide comprehensive and detailed information regarding the work undertaken by the project team, and should include a description of the product(s) created as solution(s) to the project problem. Students should determine the structure of the Write-up, whilst incorporating the recommended content below.

The recommended length of the report is 5000 words. This is however dependent on the project. The most important criteria is that the project has been well documented in the Write-Up. Appendices can be included.

Individual Interview

As a final assessment task in the project, each studentis expected to discuss contribution and learnings in a 10-15 minutes interview with the lecturer. You will showcase your project portfolio and answer questions around your contribution to the project.

Vision - Why we need to reward people.

Q - How people limited steam space.
Q- if there are continuing problem what are alternatives.
Q - Experience of / company - Recognize their effort
Q - Company about Issue

Note: Need only write up and presentation.

Attachment:- Project Details.rar