​LEADERSHIP ASSIGNMENT

PROJECT PLAN

Project Name: Pallet

Project Manager: Hiranmayi Pechetti

 1. ​Project Overview

1.1 ​Purpose, Scope, and Objectives

This document will provide all of the requirements for the

project pallet. It will serve as a reference for developers,
consultants and customers during the development of the
system.

The purpose of this product, Pallet is to implement a safe and 

secured cashless transaction system. It also includes bus ticket 
reservation. This e-commerce application can also be used to 
pay for mobile recharge. The app contains a shopping cart where 
users can buy commodities like groceries, clothes, and other 
products of their choice. The users can link their wallet to their 
respective savings account and have an effortless transaction 

This software enables the user to perform a range of operations 

making their lives easier and more manageable. The use of this 
application in different domains such as shopping and ticket 
reservation ensures that the app is well-advertised and popular 
amongst the people. Advertising to other companies generates 
revenue. The main goal is to make transactions hassle free. 

The main objective is creating a Web API, and sample web

and mobile, interfaces that demonstrate the use of the API.
The goal is to provide and help the client reach and support its
customers in a quick and easier way by questions answered.

1.2 Product features

● Secure Login for authenticity 

● Hassle-free transactions online 
● Booking movie tickets  
● Payment for mobile recharge  

1.2 Product features

1
 ● Secure Login for authenticity 
● Hassle-free transactions online 
● Booking movie tickets  
● Payment for mobile recharge  
● Profile management 
● Shopping cart management

1.3 ​Assumptions and Dependencies

Operating System: The application will be developed for Android 

platforms.  
 
Battery: The application does not consume too much battery.  
 
These assumptions may change during the course of the project 
 
There are no dependencies on other projects. This application is 
built from the start 
 
1.4 ​Design and Implementation Constraints 
 
● Users will have to download the application to their phones 
to download it. 
● Only Android users will be able to download the app. 
● Minimum 2GB RAM and memory space of 200 MB 
required. 
● Dart should be the programming language used in 
implementation with Flutter.  

2. ​Project Plan

Iterative planning

Introduction

2
The team has to be introduced to iteration planning in order for the team
to have a well defined objective when creating the software application
with realistic goals in mind
Vision and Roadmap
A hawkeye vision of the project documentation and a roadmap of the
features involved will help a team work consistently
Number of user stories fit
It is essential to know what are the user stories that can be performed by
each team member
Current Status
The team understands progress in real time
Iteration Theme / Name
(Not Chosen) It is not of utmost necessity to have nomenclature for an
iteration. In our project, iterations are a mix of different functionality. It
will be better to name each functionality than a whole iteration
Prior Data
Our project does not need any type of prior data
Dates
Target dates are highly important for the team to be able to strictly
adhere to deadlines and keep the releases moving fast
Capacity
It is important for the Scrum Master to have an estimate of each
member’s capacity of work in order to be able to provide work.
Issues / Logistics
Important to understand the areas where the team is getting stuck.
DOD
Necessary for the team to understand when a particular functionality is to
be declared as done
Backlog Extract
Must be updated with every module that is completed
Tasking
Important for the team to divide user stories into tasks in order to finish
each user story in an efficient manner

3
 Issues and Risks
Probable riska have to be calculated and issues (such as overshooting of a
deadline due to lack of availability of certain team members)
Dependencies and Assumptions
We need to take into consideration several aspects (such as bank and
credit card balance) in the Payment Wallet Application
“Commitment”
It is important that every member commits time for their part of work.
Actions
Every team member must perform their work in accordance to the plan
of action set up by the team
Retrospect

Meetings are fuelled by feedback from previous meetings

 
Task  Goal  Deliverable  Week 

Project  1. Formal Definition of  Terms of Reference  1 

Initialization  project Scope.  and contract, Core 
phase  2. Define team.  System 
3. Create project hubs.  Specifications. 
2. Preparation of legal 
contract. 
3. Review and Signing of 
contract. 
 
 

Requirement  1. Determine Business  Project plan, Team  1 

Analysis  objectives.  definition. 
phase  2. Formalize decision 
making. 
3. Produce project plan. 
4. Client review and 
Evaluation. 

Design  1. Application Design  Application  2 

2. Data Modelling 
3. Database Design 
4. Interface Design 

4
 5. Client Review and 
Evaluation 

Development  1. Interface design  Fully functional   3 

implementation  Application,Testing 
2. Coding  protocols and test 
3. Testing  case 
4. Client Review and 
Evaluation 

Deployment and  1. Set-up and  Accessible System  3,4 

Documentation  configuration of  and user manual. 
Phase  servers  
2. Domain 
registration 
3. Hosting of the 
developed system 
4. Client Review and 
Evaluation 
5. Preparation of 
users manual 
6. Administrators 
Training  

Project  1.Complete System    4 

Termination   handover 
2.Task technical staff 
to change 
authentication 
information. 
 

Support Phase    Bug fixes and minor  4 

adjustments 

3. ​Teams/ Consultants/ Freelancers Involved and Timelines  

● A local team [1 project leader (Myself) and 2 consultants(C-1,C-2)] that 

deals with the client needs and coordinates the initiative. 
 
● A remote team in London specialized in frontend programming [2
consultants (FP-1,FP-2)]

5
 ● A remote team in Mexico [2 consultants (BP-1, BP2)] that will help
you with the backend programming.
● A freelancer (F-1) specialized in software-ergonomics based in
Singapore.
● A freelancer (F-2) designer in charge of the final look and feel of the
software based in London.

Agile Methodology

Task Responsibility Start End Days Status

Sprint 1  7/12 2 Not started

Project Initialization  Myself,C-1,C-2 7/12 9/12 2 Not started

phase

Requirement Analysis  Myself,C-1,C-2 7/12 9/12 2 Not started

phase

Sprint 2(​Design​) + Client 10/12 16/12 4 Not started

review (Sprint 1)

Application Design FP-1 10/12 14/12 2 Not started

Data Modelling  Myself, F-1 10/12 14/12 2 Not started

Database Design BP-1 10/12 14/12 2 Not started

Interface Design  F-1 10/12 14/12 2 Not started

Client Review and  Myself, C-1, C-2 14/12 16/12 2 Not started
Evaluation 

Sprint 3 (Development)  16/12 26/12 6 Not started

Interface design  FP-1,FP-2 16/12 21/12 4 Not started

implementation 

Backend Coding  BP-1,BP-2 21/12 24/12 4 Not started

Testing  F-1 21/12 25/12 5 Not started

Client Review and  F-2 26/12 26/12 1 Not started

Evaluation 

Sprint 4 (Deployment and  23/12 31/12 7 Not started

6
Documentation Phase) 

Set-up and configuration  BP-1,FP-1 23/12 24/12 2 Not started

of servers 

Domain registration  C-2 26/12 26/12 1 Not started

Hosting of the developed  Myself 28/12 29/12 Not started

system 

Client Review and  Myself,C-1,C-2 29/12 31/12 3 Not started

Evaluation 

Preparation of users  C-1,BP-2 28/12 31/12 4 Not started

manual 

Administrators Training   Myself 28/12 29/12 2 Not started

Sprint 5 (Project  2/12 4/12 3 Not started

Termination) 

Complete System  Myself 2/12 4/12 2 Not started

handover 

Task technical staff to  Myself 2/12 4/12 1 Not started

change 
authentication 
information. 

Support Phase  F-2 4/12 4/12 1 Not started

The dates have been assigned keeping in mind the working days of the
week.

4. Tasks for the Project Leader as per the Assignment

- ​Set up a project plan for the 4 weeks

● A detailed project plan with it’s tasks, deliverables, goals

and weeks has been provided in tabular ​ ​form in section 2.

-​ D​efine a weekly communication and exchange schedule

● The Project plan has been split up into 5 sprints.Team

review is conducted after the end of every sprint.There are

7
 also daily Standup meetings scheduled at the end of the
day to ensure the task has been completed successfully.

- ​Define a team-work protocol on how and when to share information and

work in progress

● The team will continue to follow Agile methodology approach. AGILE

methodology is a practice that promotes continuous iteration of
development and testing throughout the software development life cycle of
the project. At the end of every sprint, user acceptance is performed.​Daily
Standup meetings are scheduled at the end of the day to ensure that the
task has been completed successfully.

- ​Define feedback loops with all people involved

• ​The Review meetings after every sprint , Stand-up

meetings that are conducted on a daily basis ,User
Acceptance Testing will act as the feedbacks for all
the ​ ​consultants and stakeholders involved in the
project.

- ​Choose the software, apps and collaboration tools that you want to use to
run the team

● To run the team ​accelo​ software will be used. It is a software that helps to
set up milestones and timelines, tasks, and dependencies and more, while
giving us the flexibility to adjust to any ad-hoc changes that may occur
through the project plan.

- ​Define a coherent compensation model for all participants

If the resources miss the deadlines the variables are deducted.

Since F_1 and ​ ​F_2 are freelancers no variable is deducted.

8
 Resource Base Variable OTE($)
Pay ($) ($)

C-1 6000 0 6000

C-2 6000 0 6000

F-1 3000 0 3000

F-2 600 0 600

FP-1 6500 1200 7700

FP-2 6500 1200 7700

BP-1 6500 1200 7700

BP-2 6500 1200 7700

Myself 12000 0 12000

Total 58400

- ​How will you make sure that your team can work together?

Working digitally results in employees not being able to sit, talk, and
communicate face-to-face which can lead to a disconnected team effort. In our
case we have employees working in different time zones which adds even more
complexity to this issue. To make sure that the team can work together we can
make use of collaborative tools like Skype and Microsoft Teams, zoom, google
hangouts make it really easy for team members to communicate, carry out fully
fledged meetings, collaborate on share screens, give feedback. These tools open
up plenty of opportunities to keep in touch with your peers at all times, increase
clarity amongst employees and develop better interdepartmental relations.

- ​What will you do in order to ensure the team’s motivation during the 4
weeks?

Keeping your team’s motivation and morale high is a very important task
especially when you have a shortened deadline. Some ways we can do this are

● Celebrate And Acknowledge The Small Wins:

9
 Acknowledging the efforts of your staff or team is key in order to drive
employee engagement and motivation. Each acknowledgement, regardless
of how big or small, triggers the reward circuitry within our brains which
makes us feel a sense of achievement and pride. This leads us to act and
focus on what triggered that feeling in the first place and causes us to
strive to achieve more.

● Add Some Fun To The Working Week:

Working day in and day out can be tiresome and will demotivate the
employees. We can have “Happy Hours” every once or twice a week
where all the employees just sit, have a drink or two and do some fun
activities to relax their minds. This will help them regain focus and work
with a fresh mind and get better results.

● Be Mindful And Supportive:

Many times the employees are under pressure with personal issues. Be it a
sick family, or a large loan. This may demotivate the employee and he
may not work to his full potential. Understanding your employees, talking
to them and giving them support is the best way to motivate them.

​How will you manage to reduce the normal estimated duration from 6 to 4
weeks?

● Taking a big task and splitting it down into two or more smaller tasks each
of which could start ahead of the completion of the previous one will help
reduce time it takes to finish a particular task.
● Terminate false reliance and scheduling work in parallel.
● Setting up scope before we gather all the team members reduces inefficient
time at the beginning of the project.
● The team members own priorities and the project goals interference should
be minimized.

- ​What are the 5 questions you would like to ask your boss the day he/she told
you your role in this ​ ​project?

1. What are your expectations of me as an employee in this position?

2. What made you give me this role?
3. What kind of skills and training should I seek out to get the best results?
4. What should I know about the workflow and management style of this

10
 project group?
5. Can I expect a hike in salary if my performance is good?

- ​What are the most important differences between a project like this
and a project with all members ​ ​physically together? What are the
benefits? What are the negative aspects?

Benefits of working in a project where all members of team have to

communicate digitally are :

● work-life-balance

Employees no longer have to spend hours commuting to and from

the office, saving them time for leisure.

● Improved productivity

Digital collaboration tools can help with a ton of administrative

tasks in a jiffy, saving time for employees to spend time on other
value-adding activities. More work is done in fewer hours due to
fewer distractions like meetings, conversations, and noisy
coworkers.

Negative aspects of working in a project where members of team have to

communicate digitally are:

● There are always disturbances like bad network connection or

maybe the family members intervening in an important meeting.
● Loss of interpersonal communication skills.
● Data security can be a major challenge, especially if security
frameworks are not in place to protect your organization’s data
and information.

- ​What are the 5 takeaways you would get and what would you advise
another project leader in your ​ ​situation?

1. Understanding each employee and knowing his strengths and potentials

will help you and the employees a lot.
2. Do your best to have transparency between you and your employees.
This will lead to a comfortable and an open working environment for

11
 everyone.
3. Have frequent discussions and meetings as a group as well as with each
employee personally. This will help you understand the group’s and the
individuals thought process and ideas on the project.
4. Always have a proper plan and structure for the project. Have goals and
do your best to achieve them in the planned time duration.
5. When you have to constantly meet deadlines, you and your group will
easily get demotivated and exhausted. And this will lead to poor
performance and below par results. Always keep a proper work life
balance. This will lighten up the workplace and the results will be good.

12