90 min, writing

Give some specific IT projects, write down steps to manage an IT Project?

What should a manager do?

How to manage a project?

What steps? And describe each of them

Project managers play a key role in helping projects and organizations succeed. They must perform various job duties, possess many skills, and continue to develop skills in project management, general management, and their application area, such as IT. Soft skills, especially leadership, are particularly important for project managers.

Many people try to present the proposal, they expect the community to read the plan

If oke, then they give the budget

If the project is successful, then the gains are really bigger than what we spent.

Base on what we consider a project fails: do not satisfy the three important keys: scope, time, and cost.

We don't limit the size, people, or time of the project

IT project involves HW, SW, networks

In the end, we deliver some results, products

Good case study: nowadays, many people use fake documentation, such as real estate papers.

So, we can use the solution with the blockchain technique

The methodologies

Project Management Methodologies - Everything You Need To Know (teamwork.com)

One of the Other key factors besides the three important keys is Quality

Quality is a key factor in projects, as is customer or sponsor satisfaction.

What are resources? Stakeholders, team member, user, tools....

Stakeholders are people involved or affected by project activities.

Tools, techniques: Gantt Chart is one of the tool for creating a schedule

Draw Gantt Chart,

Step 1: Analysts determine requirements

Step 2: Designing - Designers

Step 3: Programming - Developers

Step 4: Testing - testers

Step 5: Maintenance: involves many people, but the main is the quality manager.

What skills are needed for a PM? 26

Schedule

Care about dependencies.

Need the WBS and estimates before creating the schedule.

The PM should understand: WBS, dependencies, resource allocation, critical paths, Gantt charts, earned value.

Review

what to review: service, software, or something called a work product.

many ways to review depending on the product.

purpose: to save time and effort of the team.

Requirements

Why do we need requirement analysis? We work with clients, so we need to make sure we satisfy their needs. SO we need someone to take care of this, an analyst (business, software)

The behaviors of the SW must be determined before it is built.

Needs to have the skills

A good tool for this is UML

Design and Programming

what in the design: pictures, flowcharts, dataflow diagrams, database design diagrams...

mockups

many users find it hard to understand the design.

Testing

when the SW has been built, it's time to look back and make sure it meets all requirements.

test plan is a list of tests to be performed: what, who, when, how

test plan is valuable because it is easy to review.

test cases are similar to use cases

Diagnosing Problem

Understanding Changes

Changes are to get a better SW

But, many people feel uncomfortable

Need to understand why people feel like that then we can deal with the uncomfortable feelings

Improvement

Extreme programming

Split big duration into the smaller periods, each with its milestones, after each period, release one built,