Webinar Session (New Era University, College of Information Science & Tech) - Process and flows of an IT project - 2022 Apr 08 attended by 280 students. Objective: Provide students an overview of how IT Projects advance today's real world. Get a head-start and effortless transition as you join an organization. INTRO Understanding the process and flow of an IT Scheme will enable you to know your advantage in project development. Project Managers, IT Leads, and C-Level Executives expect your best foot forward when joining a company. Obj: Provides students a top-level view on how an IT project moves in the real world in order to get a head-start and easy transition as you join a the working world. I know that most of you are graduating students or nearing the internship programs, some of you might be in between or are considering becoming a freelancer which is a smart move considering the advent of the remote work in the “new normal” then you will certainly benefit from this topic. My favorite thing abt my work is simplifying complex information. So I divided the phases and flows into 5 levels Now keep in mind, it can be as extensive depending on the complexity of an IT proj but this is roughly the breakdown of each stage. Let’s have a look at: - what happens in each phase - what are the processes and tools are, - who are involved/ ppl you’ll be meeting, - what you should do and how you can be useful!

1. Process and
flows of an
IT Project
April 08, 2022
Speaker: Casey Ordoña, MBA

2. INTRO
Understanding the process and
flow of an IT Project will arm you
with an unfair advantage in the
working world.
Project Managers, IT Leads, and
C-Level Executives expect your
best foot forward when joining a
company.

3. There are different types of IT
projects: web development,
software development, mobile
app development, network
configuration, software
implementation, hardware
installation, database
management, and IT
emergency recovery, etc.

4. ABOUT THE SPEAKER
● Took lead roles in IT agencies, was previously based in Singapore,
Australia, US, and she’s now back in the Philippines.
● Oversees Digital Transformation project ranging from healthcare, retail,
gov’t, from brands like Google, Samsung, Shopify, Shell Oil, among others
● President / Owner of a Marketing & Tech Consulting firm: Evolve Digital
Media Consultancy
● Awarded among Top 100 Influential Filipino Women in Linkedin
● NEU/Eranian batch of 2010
Hi, I’m Casey!

5. Phases of an
IT Project in
5 levels

6. IT PROJECT
Conception & Initiation
01

7. Conception & Initiation
People you will meet -
Client-side: Product owner, IT head, PO, Mgrs, etc
Vendor-side: Sales/Account director, Project Mgr,etc
Give an overview and intro about themselves - get to
know. Provide the problem or present the brief.
Outcome:
Project will go through or won’t.
Pro-tip:
Assess the capability:
projects done before
& team structure.
2 parties involved:
Client-side and
Vendor-side

8. Conception & Initiation
Questions to be answered in the initiation phase include the
following:
● Why this project?
● Is it feasible?
● Who are possible partners in this project?
● What should the results be?
● What’s the timeline like and who are involved?
Pro-tip:
get a hold of the
meeting minutes,
persons and roles
involved. Who’s who.

9. IT PROJECT
Definition & Planning
02

10. Definition & Planning
Scope of work. Solution architecture - Process flow,
Wireframe, Mock up designs. Timeline. Breakdown of
Milestones. Money talk / Budget. Risk management.
Communication plan.
Tools: Means of communication for different channels,
by channels, I mean Internal comms, External comms,
sometimes there are hybrid.
(Slack/Skype/Email/Teams/Zoom/Hangout/Meets) <-
good to get yourself acquainted on all these
What’s important for you is to know the stages and
deliverables. How often the meeting is. Who’s the PIC
and team you will be working with.
Tools:
Slack/Skype/Email/Te
ams/Zoom/Hangout/
Meets
Pro tip:
Be organize.
Familiarize yourself with
the team and processes

11. Common terminologies you will encounter
At this time, roles and responsibilities are clearly defined, so everyone involved knows what they are accountable for.
Common terminologies you will encounter
Business Req’ts Document (BRD) – A document that clearly defines the business need, project benefits, objectives,
deliverables, and critical milestones. A scope statement may change during the project. Still, it shouldn't be done without
the approval of the project manager and the sponsor.
Work Breakdown Schedule (WBS) –This is a visual representation that breaks down the project's scope into
manageable sections for the team.
Milestones – Identify high-level goals that need to be met throughout the project and include them in the Gantt chart.
Gantt Chart – A visual timeline that you can use to plan out tasks and visualize your project timeline.
Communication Plan – This is particularly important if your project involves outside stakeholders. Develop the proper
messaging around the project and create a schedule for communicating with team members based on deliverables and
milestones.
Risk Management Plan – Identify all foreseeable risks. Common risks include unrealistic time and cost estimates,
customer review cycles, budget cuts, changing requirements, and lack of committed resources.

12. Example
Solutions
Architecture
Diagram

13. IT PROJECT
DEVELOPMENT
03

14. Development
● This is where the actual work happens and
hence the longest among all the phases.
● Let me introduce you the tools common at
this stage: Asana, Trello, Jira, Github, AWS,
etc
● Different development methodologies or
framework: Agile, Scrum, Waterfall, Kanban.
Tools:
Asana, Trello, Jira, Github,
AWS, etc
Dev frameworks:
Agile, Scrum,
Waterfall, Kanban
Pro Tip:
Get Certified.

15. Frameworks & Methodology
Unique
Characteristics,
Applications, Pros,
and Cons Waterfall
Agile
Scrum
Kanban
● Suitable for smaller projects with well
defined requirements
● Perform verification and validation
● Extremely stable
Pros
● Testing period is possible only in last three
phases
● Documentation takes much time
● Doesn’t much prioritize client or end user
Cons
● More productivity
● More transparency
● Rapid and continuous delivery
● Project deliver happens quickly and
efficiently
● Large projects are divided into sprint
● Focus on continuous delivery of projects
● It reduces costs
● Not useful for small development projects
● Lack of documentation and difficult
trackability due to lots of changes
● Not appropriate for larger projects
● Needs experience to involve in scrum
● Doesn’t consider deadline for the projects
● Kanban is not an independent tool
● Kanban doesn’t support dynamic
environments

16. IT PROJECT
Performance &
Quality Assurance Control
04

17. Performance & QA Control
You will encounter Staging Site / Testing
Environment here.
User Acceptance Test comes here.
Client review. Revisions.
Tools:
Common tools: Google launcher. Browser tester.
This is the crucial part. Companies have a set of
SOP/Checklists they will have to follow on these.
Tools:
Browser Emulators
Soft Skills
Rational thinking & EQ. Listen.
Wear different hats as a user.
UAT comes here.
Client review.
Revisions.

18. Emulator Tool: Chrome Dev Tool

19. IT PROJECT
Launch / Deployment,
Implementation &
Handover
05

20. Deployment & Handover
➔ LAUNCH
➔ Post-deployment tasks
➔ Monitoring period
➔ Training and Handover
➔ Sign off
Introspection: Impt to have a list of what
worked and didn’t.
Tools:
Report and
Post-mortem
analysis
Pro Tip:
Keep a hard
code copy on the server.
&
Introspection

21. IT Project Review structure
Tools:
Google doc, Microsoft
Onenote, or Google
Keep or Apple Notes
Pro Tip:
Cloud-based

22. RECAP
What questions do you have?

23. THANK YOU.
Let’s connect!