PROJECT MANAGER 2.

0
SOFTWARE PROJECT MANAGEMENT

School:
Universidad Politécnica de Durango

Student Name:
Vargas Fernández Ashea Saray

Teacher´s name:
Vanessa Ramirez

Date:
07/11/2022
Content Table
1. SYSTEM SOOKAMI KPOP SHOP ................................................................... 4
1.1 Initiation ...................................................................................................... 4
1.1.1 Requirement gathering from the stakeholders ..................................... 4
1.1.2 Develop project charter ........................................................................ 4
1.1.3 Deliver System project charter ............................................................. 5
1.1.4 Feedback from the stakeholders.......................................................... 5
1.1.5 Approval of charter from the stakeholders ........................................... 5

1.2 Planning ..................................................................................................... 5

1.2.1 Develop the System project scope statement ...................................... 5
1.2.2 Choose right people for the project and form teams. ........................... 6
1.2.3 Hold a meeting before initializing the project ....................................... 6
1.2.4 Develop Project Plan ........................................................................... 6
1.2.5 Submit Project Plan ............................................................................. 6
1.2.6 Milestone: Project Plan Approval ......................................................... 6

1.3 Execution ................................................................................................... 7

1.3.1 A Meeting marking the initialization of project ...................................... 7
1.3.2 Gather User requirements and check feasibility .................................. 7
1.3.3 Develop System design and architecture including modules and
functionalities implemented .............................................................................. 8
1.3.4 Gather necessary hardware for development ...................................... 9
1.3.5 Developing System according to the strategy agreed upon. ................ 9
1.3.6 Deploy the System made for testing .................................................... 9
1.3.7 Testing Phase ...................................................................................... 9
1.3.8 Deploy the System to train and get feedback from a selected group of
users 9
1.3.9 Release the System............................................................................. 9

2
 1.4 Control...................................................................................................... 10
1.4.1 Project Manager overlooks the development phases plus the planning
phase 10
1.4.2 Development status fed to the manager ............................................ 10
1.4.3 Risk analysis and management ......................................................... 10
1.4.4 Accommodating new user requirements ............................................ 10

1.5 Closeout ................................................................................................... 10

1.5.1 Audit .................................................................................................. 11
1.5.2 Document Lessons Learned .............................................................. 11
1.5.3 Maintain Project Record .................................................................... 11
1.5.4 Send the record for review and approval ........................................... 11
1.5.5 Archive the record and project documents ........................................ 11

3
1. SYSTEM SOOKAMI KPOP SHOP

1.1 Initiation
Due to the pandemic, many companies looked for a way to make their sales online
since in this way they could continue selling without limitations due to physical
contact, that is why the CEO of Sookami allowed us to digitize their business as
the process that was carried out this year.
The work team in charge of the "SOOKAMI KPOP SHOP" project was made up of
Juan Fernando Amador Miranda and Ashea Saray Vargas Fernandez who worked
providing the knowledge obtained previously in software engineering career.

1.1.1 Requirement gathering from the stakeholders

For the collection of requirements, we asked for the collaboration of our external
advisor to have different virtual meetings in which we were able to establish the
requirements that were asked of us based on their requests, in addition to
generating restrictions and the objectives of the project.
The types of requirements we gathered were:
• Specific requirements
• Functional requirements
• Common interface requirements
• Non-functional requirements
• Legal requirements

1.1.2 Develop project charter

The project charter is a document that lays out the project vision, scope,
objectives, project team, and their responsibilities, key stakeholders, and how it will
be carried out or the implementation plan. It is also known as the project statement
and project definition report.
In this specific case, the requirements document and the stay report served as a
project charter and it helped us to establish points such as participation in the
project, justification, purposes, goals, etc.

4
1.1.3 Deliver System project charter
The delivery of this document was carried out virtually since we were still limited by
the contingency caused by COVID-19, even so, to seal the creation of the
document, a single review date was established, accompanied by the review mark
by the external advisor. and internal.

1.1.4 Feedback from the stakeholders

On the part of our external advisor we had no comments since the documents
were reviewed and validated at the time, so it is understood that he was satisfied
with the results.
On the other hand, the institutional adviser corrected some points of the report and
asked us to expand on some points.

1.1.5 Approval of charter from the stakeholders

The project charter document was accepted by both parties at the time of the stay
evaluations.

1.2 Planning
Project planning and management is an ongoing process during the project life
cycle.

1.2.1 Develop the System project scope statement

The following statement was the scope established together with the external
advisor during the development of the project and was part of the content of the
requirements document.
“The product that is planned to be developed is a software that works as an online
store and serves to introduce SooKami to electronic commerce (e-commerce). All
this in order to get more potential customers and facilitate sales.”

5
1.2.2 Choose right people for the project and form teams.
For this project I chose Juan Amador as a colleague since being close to him I am
aware of the skills he has and above all his sense of responsibility that guides
others to maintain an adequate work pace.

1.2.3 Hold a meeting before initializing the project

At the beginning of this project, a meeting was held with the external advisor who
was in charge of transmitting his interests and goals in a more informal way before
starting everything.

1.2.4 Develop Project Plan

For this phase we decided to use the waterfall methodology which is based on
carrying out different phases. Each phase begins only when the previous one has
ended.
On the other hand, to work on the development of the project we also decided to
follow a previously designed work plan since it was a requirement requested by the
university as part of the preliminary project.

1.2.5 Submit Project Plan

The work plan was sent only to the institutional advisers who were in charge of
approving the dates and scheduling meetings to verify that the work plan was
fulfilled.

1.2.6 Milestone: Project Plan Approval

As I mentioned before, the work plan was previously approved in order to start the
stay process.
On the other hand, the external advisor let us work freely and we only had
meetings to validate the project process and have control of changes.

6
1.3 Execution
After setting the objectives and planning it in detail and in writing, it is time to
execute it.

1.3.1 A Meeting marking the initialization of project

The first official meeting with the external advisor was held virtually, in this meeting
we introduced ourselves to create a better work environment and established some
agreements regarding the project such as confidentiality and the specific
requirements that our client had. We also included this point in the requirements
collection document and it was as follows:

Specific requirements
Among the requirements that must be met by the system to be developed are the
following:
RQ1. Allow a login.
RQ2. Allow to use the Create, modify, and delete the details of
the account and the products in the cart.
RQ3. Have a photo carousel.
RQ4. The system must be able to accept payments.

1.3.2 Gather User requirements and check feasibility

For the collection of requirements, we scheduled a meeting where we dedicated
ourselves solely to the creation of the requirements based on previous projects, in
this way it was easier to guide the client on how to present their requests.
For the moment that we made stays, feasibility was part of the points that we
established in the requirements collection document.

7
1.3.3 Develop System design and architecture including modules
and functionalities implemented
In this project the design is based on similar pages that were already active,
however it was adapted to the image and colors used by SOOKAMI.
For the modules we created a diagram of the main modules as part of the
explanation of product functionality that was given to the client, so the diagram is
written in Spanish.

The functionality of the project that we established is the following:

“The system is a program for the sale of Asian products, according to the first
requests of the client, it must receive orders for the products, show an updated
stock, be able to pay with different means of payment such as cards, PayPal, etc.
Likewise, it must show images of the products for sale and can show a shopping
cart.”

8
1.3.4 Gather necessary hardware for development
For this project, no specific software or hardware was needed, so each of the
members could work with our personal devices.

1.3.5 Developing System according to the strategy agreed upon.

For this project we use Angular which is an open source web application
framework developed in TypeScript, maintained by Google, used to create and
maintain single page web applications.

1.3.6 Deploy the System made for testing

For this project we carry out tests manually by accessing the different modules to
find possible errors.

1.3.7 Testing Phase

When the system was finished, my co-worker Juan Amador was in charge of
testing, especially in the payment module, since the extension we used was new to
us.

1.3.8 Deploy the System to train and get feedback from a selected
group of users
In the final phases of the process, our internal consultant was asked to check the
page to give us her professional opinion and she asked us for some changes
related to the design.

1.3.9 Release the System

The system was finished with the client's requests and was released on a website.

9
1.4 Control
The main function of effective project control is to provide the client and the project
manager with all the resources with which the execution of the overall project can
be organized, supervised and finalized in such a way that cost and planning
objectives are met, as well as with the standards.

1.4.1 Project Manager overlooks the development phases plus the

planning phase
The overlook of the project was carried out in the final phase when the evaluations
were carried out, by the school a review of what we put in the work plan was made,
it was verified that everything was completed.

1.4.2 Development status fed to the manager

The development status was updated for the institutional advisor, however we had
to update the external advisor at the time of finishing the project.

1.4.3 Risk analysis and management

At the time of the stays we do not create a risk analysis.

1.4.4 Accommodating new user requirements

During the stays process, we established the assumptions and dependencies of
the project in case the company had important changes in its image.

1.5 Closeout
The closing of the construction is the final phase of the process of realizing a
project

10
1.5.1 Audit
For the final part, we have an audit with our internal advisor who checked that
everything was in order and that it worked correctly.
On the other hand, the audit with the client included giving him the user manual
and explaining how the modules worked and how he could use them.

1.5.2 Document Lessons Learned

One way in which we documented what we learned was at the time of making the
report since that was part of the conclusion that we drew.

1.5.3 Maintain Project Record

A record was kept throughout the process since, being an institutional process, it
was part of the requirements to validate it.

1.5.4 Send the record for review and approval

There was no need to deliver a record to the business advisor since it was kept up
to date and he did not ask us for any document besides the user manual.
On the other hand, the report of the stays was delivered to the university where we
presented all the records we had of the project.

1.5.5 Archive the record and project documents

Finally, we deliver all the content created to the client and say goodbye to the
project without closing ourselves off from the possibility of working on it later. The
final phase for the university included more requirements, so once all the records
were accepted and having a grade on the report card, we were able to conclude
the project.

11