Project managers Knowledge
Quick notes about what is Project 🏁
Project :
-temporary endeavor
-unique
-meets expectations
-end outcome-- documentation
Program - coordinated management of a group of:
- projects
- subprograms
- activities
click to edit
Portfolio-collection of programs, projects
Project balance:
Scope
*Quality
Schedule
Budget
Never forget about balance of :
Resource
Risks
Project keeps improvement and changes until his death/closure
Integration Process:
-Project Charter(Purpose of Project;Deliverables;success criteria; High-level requirement; Assumptions; Project description;High-level risks;summery:Milestones, budget;Stakeholder list;Project approval; Details of PM;Sponsor Details.)
-Project management Plan
-Direct and manage project work
-Monitor and Control project work
-Perform integrated change control
-Close Project or Phase
Charter gives authority for PM to use Money and Resources
-Generic
-Predictive
-Iterative
-Adaptive
-Specific controls and processes are used to Accomplish each Phase's Goals
Process(set of activities) are always Product oriented
Output = input + Technic
click to edit
Initiating:
Define Scope
Obtain Finance Commitment
Identify Stakeholders
Select PM
Produce
Project charter
Stakeholder register
Vision
Scope
Goals
Problems
Risks
click to edit
Executing
Coordinate people and resources
Manage Stakeholder Expectation
Perform activities that flow
Make sure all sides know what to do and what to expect
Monitor and control is Critical
-track and review
-identify areas to change
-Initiate changes
-Control Changes
-Recommend correction actions
-Monitor activities in relation to plan and baseline factors of influence.
Close- process what to do when Project is aborted, cancelled, critical situation
What needs to be done:
-get customers approve to close
-conduct reviews
-record impacts
-Document
-Learn your lessons
-RELEASE PROJECT RESOURCES
Planing
Establish Scope
Define objects
Develop course of actions
Output
Scope
Schedule
Cost
Quality
Communication
Risks
Procurement
Stakeholder engagement
Human Resources
Obtain stakeholders buy-in
click to edit
click to edit
Knowledge area - concepts, terms, and activities that make up a field.
click to edit
click to edit
click to edit
click to edit
Integration
when changes effects all
Project chapter - official start of project
Project management plan (DOCUMENT how to manage, execute, test, close, perform, communicate)
Monitor and control project work
Change control
Close project/Phase
SPONSOR DEVELOPS CHARTER ; PROJECT MANAGER is IDENTIFIED; SENIOR MANAGER APPROVES CHARTER
Project management plan ,
includes:
Scope plan
Requirements plan
Schedule management plan
Cost plan
Quality measurement plan
Process improvement plan
Human resources plan
Risk plan
Procurement plan
Change plan
Configurations plan
Stakeholder management plan
Scope baseline
Schedule baseline
Cost baseline
click to edit
PROJECT MANAGEMENT INFORMATION SYS.
Cost resourcing tool;financial; performance indicators; Databases; Project records.
Output;
Change(correct; repair; prevent.)
Work performance reports - help to generate decisions, actions or awareness.
(status; memos; justification; information; recommendation; updates.)
Monitor and control Project work
Tracking; reviewing; reporting progress to meet objectives defined in the project management plan.
Inputs
Project management plan
Cost forecast
Validated Changes
Work performance info
Enterprise environmental factors
Organization process assets
Outputs
Change request
Project manage plan updates
Work performance report - data converted to useful information and then reviewed to see if changes need to be made.
Analytical techniques:
Regression analysis; Grouping analysis; Casual analysis
Root cause analysis; Earned value management; Reserve analysis.
Perform Integrated change control - reviews request for changes and approves or rejects changes.
Configuration management activities
Config status accounting
Config verification and audit
Input
Work performance report
Change request
Enterprise environmental effects
Organizational assets
Tool
Manual or automated tool that manage change requests and decisions
Approved changes
Change log
DIRECT AND MANAGE PROJECT WORK
Performing work in project management, plan and implement approved changes
- corrective actions
-preventive actions
-defect repair
Input:
Enterprise environmental factors
Organization process assets
Tool
Project management informational system
expert Judgement
Output
Deliverables
Project management plan updates
Work performance data (raw data)
Change request
Project docs update
Project Scope Area - Very critical
-Plan Scope management
-Collect requirements
-Define Scope
-Create WBS
-Validate Scope
-Control Scope
click to edit
Close Phase or Project
Inputs
Project management plan
Accepted deliverables
Organn. Process assets
Tool
Expert judgement
Analytical techniques
Meeting
Output
Final product
Service or result transition
Organizational process assets updates
Project files
Project/Phase closure docum.
Historical information
click to edit
click to edit
click to edit
click to edit
Define scope
Process of developing - a detailed description of project and product.
Input
Scope management plan
Project charter
Requirements docs
Organizational process assets
Tool
Expert judgement
Product analysis
Facilitated Workshops
Output
Project scope statement
Project docs update
Product break down
System analysis
Product analysis
Requirements analysis
Values analysis
Plan scope Management
- document how project will be defined
validated and controlled.
--Project manager oversee scope
--Changes are handled in controlled manners
--Project manager controls change factors
-identify work for Scope
-No Gold plating
click to edit
click to edit
WBS DECOMPOSITION
Output
Scope statement
WBS
WBS dictionary
Point everything is critical
Decompose work to small estimated peaces to:
hour
development in points
estimate in costs
Each work is placed just once
All work is included in WBS
click to edit
click to edit
click to edit
click to edit
Validate Scope
process of formalizing acceptance of the completed project deliverables.
Input
Project manage plan
Scope baseline
Scope manage plan
Requirements documentation
Requirements acceptance criteria tracks project during the project
during projects life.
Output
Verified Scope
Work performance
Control Scope
Input
Project management plan
Requirements traceability
Work performance data
Tool
Variance analysis
Output
Change request
Work performance info
Plan update
Project docs. update
Organ process assets update
Reserve cost - cost for all resources required to perform and complete the activities.
Project Costs
Estimate costs
Input
Cost management plan
Human Recourse
Scope baseline
Project schedule
Risk register
Enterprise Environment
Organ. process assets
Tool
Expert judgement
Analysis est.
Parametric est.
Bottom up est
Cost of quality
Vendor bid analysis
Group decision
Output
Activity cost estimation
Basis of estimation
Project document update
click to edit
Plan cost management
Process to establish polices procedures and documentation for planning, managing, expanding and controlling project cost.
Input
Project management plan
Project charter
Enterprise environment factors
Organization process assets
Tool
Expert judgement
Analytical technics
Meetings
Output
Cost management plan
click to edit
Cost aggregation - summing lower level cost estimation association with various work packages for a given level with in the project's WBS of for a given lost control account.
Project funding requirements - forecast project cost to be paid that are derived from the cost baseline for total or periodic requirements, including project Expenditures plus anticipated liabilities,
click to edit
click to edit
click to edit
Control costs
Process of monitoring the project statuses to update cost and managing changes to the cost baseline.
Input
Project management plan
Project funding
Work performance data
Organization process assets
Tool
Earned value
Forecasting
Performance review
Reserve analysis
Project management soft.
Output
Work performance info.
Cost forecast
Change request
Project management plan update
Project doc. update
Organization process assets update
PROJECT QUALITY
click to edit
click to edit
Project Quality
Plan quality management- identifying quality req.
for the project will demonstrate compliance with the requirements
Input
Project management plan
Stakeholder register
Risk register
Requirement documentation
Enterprise factors
Organization process assets
Tool
Cost benefit anal.
Cost of quality anal.
Meetings
Output
Quality management plan
Quality metrics
Quality checklist
Project document updates
click to edit
click to edit
Control quality
Input
Project management plan
Quality metrics
Quality checklists
Work performance data
Approved changes requests
Deliverables
Project docs
Organization proc. assets
Output
Quality control
Measurements
Validate changes
Verified deliverables
Work performance inform.
Change requests
Project plan update
Docs update
Company procedures assets update
click to edit
click to edit
click to edit
Perform quality
Quality assurance - ensure process are followed as documented.
Quality Control - ensure prod. meets quality specification.
Input
Quality management plan
Process improvement plan
Quality metrics
Quality control measurement
Project document
Tool
Quality control/management tools
Quality audit
Process analysis
Output
Change requests
Project man. plan update
Project docs update
Organization process assets update
click to edit
click to edit
click to edit
click to edit
click to edit
click to edit
Seven basic quality tools
(cause and effect diagram; flow chart; check sheet; pareto diagram; Histogram; Control chart; Scatter diagram)
Benchmarking - compare projects to identify best practices, lessons learned and performance measures.
Note!! identify factors that may influence variables of product under develop. or in production.
Statistical sampling - choosing part of the population of interest for inspection.
Quality metrics - description of project or prod. attribute and how to measure it.
Human resource management
-Process of identifying and documentation project roles responsibilities and required skills =, reporting relationships and creating a staffing management plan.
Activity resource requirements
-number of stuff and dates when it is needed
Responsibility assignment matrix
- grid with each of the resources assigned to a work package
Input
Project management plan
Enterprise environment
Organ process assets
Organization charts and position descriptions
Networking
1)Launching of informal meetings
2)Trade conferences
3)Symposia
Organization theory
how team and organizations behave
click to edit
click to edit
Input
Human resource plan
Enterprise env.
Organization process assets
Tool
Pre assignment
Negotiation
Acquisition
Virtual team
Performance upraise
Conflict management(
Compromise/reconcile
Collaborate/Problem resolve
Force/Direct
Smooth/Accommodate
Withdraw/Avoid)
Output
Project stuff assignment
Resources calendar
Project management plan update
Pre assignment - members are named in advance of the project starting Negotiation
Tackman ladder of team develop (Forming; Storming; Norming; Performing; Adjourning)
Personal assessment tool - how to use resources for 100%
click to edit
Are - Communication
Types of communication:
Internal/External
Formal/Informal
Vertical up to man
Official/Unofficial
Written/Oral
Verbal/Nonverbal
Manage communication
Control communication
Control communication
*Human resource management Plan
*Tool
Expert judgement
Meeting
Output
Human resource management Plan
Roles and responsibilities
Project organization charts
Staffing management plan(When and how long)
(Staff acquisition; resource calender; staff release plan; training needs; Recognition and rewards; Compliance with regulation; contracts; polices; safety polices)
Plan Communication management
process of developing a plan for a project can be based on stakeholders' information needs and requirements
Input
Project manage plan
Enterprise env. factors
Organ process assets
Tool
Communication models
Output
Docs update
Communication manage plan
Process of manage communication- crating, collecting, distributing, storing, and disposition of project information in accordance with communication manage plan.
click to edit
-process of monitoring and controlling communication through the project to ensure the info. needs of project`s stakeholders
Output
Summery of work performance - data used as an update for stakeholders
Change requests
Risks-uncertainties on project.
Plan risk management
Identify risks
Perform quality analysis
Perform quantitative analysis
Plan risk control and management
Plan risk management
process of defining how to conduct risk management activities for a project.
Analytical technics. how to analyze potential outcomes based on variations of project or environmental Variables and their relationships with other variables.
- Budget estimation for risks
- Methodologies how to manage risks
- Roles and responsibilities in team
Quit having so many critical risks
(Quality; Human resource; Schedule; Cost; Risks)
Risk planning - process of determine which risks may affect the project and documenting their characteristics.
Tools
Brainstorming
Delphi
Root cause analysis
Assumptions analysis
Fishbone diagram
SWOT
Output
Risks register
Risk probability; Category; Urgency; Risk Break Down
Sensitivity analysis
Project Procurement - documenting process of purchase procurement , what when and how many is required for needs of project.
Make or buy analysis
Procurement management plan
Procurement docs
Output
Source criteria selection
Area Stakeholder
Manage expectations
Resolve issues
Push communication - communication info sends direct to stakeholders
Pull info - posted when stakeholders can see it
(Identify Stakeholder; Document stakeholders; Analyze and Classify; Plan and Implement Engagement; Monitor and update)
Project time
What to do:
Plan shedule management
Define activities
Sequence Activity
Estimate activity resources
Estimate activity durations
Develop schedule
Control schedule
Senior Test Engineer:
Participating in risks identification and analysis, suggesting risk response strategy.
- Translating product requirements to task specifications for Junior Test Engineers
Carrying out technical supervision of Junior Test Engineers and Test Engineers.
Identifying, solving and preventing problems that hinder software development process
- Senior Test Engineer inspects and reports on the quality of
products through the entire production cycle.
Senior Test Engineer setups and tailors software testing processes on projects; designs, documents and executes verification activities; ensures meeting schedule and budget constraints set for a project or its part; ensures effective collaboration inside testing and project teams.
Test Engineer:
Closely collaborating with development team and product experts to get knowledge / ideas / recommendations required for effective and efficient testing.
Identifying and escalating project risks, suggesting actions for risks handling.
Identifying, escalating, and helping in solving problems that hinder the tasks implementation. Helping less experienced Test Engineers in resolution of problems they faced with.
click to edit
click to edit
click to edit
Junior Test Engineer:
⦁ Position Objectives
Support development of the product with testing following existent software testing process, learning product under test, performing testing from end-user’s point of view using existent test documentation, and helping in basic testing documentation creation.
click to edit
Junior Test Engineer is responsible for:
Performing testing from the end-user perspective on the basis of the existing test documentation.
Assisting in development of basic test documentation: test cases, check-lists.
Gaining knowledge about the main functions of the product.
Reporting on task statuses on demand.
Collecting and documenting test results.
Reporting found issues to task tracking systems.
Studying new technologies, testing tools required for task processing.
Maintaining test environments and tools required for tests execution.
Collaboration with project team to achieve expected results.
Identifying, escalating, and helping in solving problems that hinder the tasks implementation.
click to edit
Test Engineer inspects and reports on the quality of products through the entire production cycle under supervision of more experienced Test Engineers. Depending on the product, may use different criteria to check the quality attributes, such as functionality, durability, safety and speed.
⦁ Position Objectives
Test Engineer designs and executes testing activities on elaborated solutions or their parts, working as a member of a project team.
a Senior Software Developer
⦁ Subordinate and report to the Architect, Team Lead or directly to the Project Manager, depending on the project team structure.
1. As a Senior Software Developer, you take responsibility for designing, implementing, unit testing and documenting software systems in time and to budget that conform to coding, architectural, quality and reporting guidelines on an internal or a customer-facing project, as well as for ongoing maintenance and support of such systems.
Contribute to development of technical project documentation and user documentation.
Participate as the technical solution owner in proposal preparation efforts, and perform knowledge transfer to the team lead / responsible software architect when the project starts
Participate in project and team meetings, provide relevant contributions and information
Participate in conference calls and face-to-face meetings with the Customer.
In case of necessity Senior SW Developer may fulfill the roles of: Software Architect (under supervision of one of department’s architects)
As a Software Developer
⦁ Subordinate and report to the Architect, Team Lead or directly to the Project Manager, depending on the project team structure.
As a Software Developer, you are responsible for design, implementation and maintenance of software solutions working as a member of a project team. This may involve personalization or development of a completely new solution for a specific customer or modification of an existing solution to make it fit with what the customer wants.
Design, implement, debug portions of software, including modules and components, complete software systems of considerably small size and medium.
Dev-test own code, check key scenarios, corner and edge cases prior to changing task development status to Done.
Peer-review design and code with middle and senior level specialists, be proactive and request reviews instead of waiting for somebody to enforce it
Participate in project and team meetings, provide relevant contributions and information
click to edit
As a Software Developer you have the powers:
click to edit
To suggest improvements in all engineering aspects of the project.
To improve your qualifications within your area of expertise at various training courses, seminars or other educational organizations.
Junior Software Developer, you
Junior Software Developer
⦁ Subordinate and report to the appointed mentor (usually one of Senior Software Developers on the team), Architect, Team Lead or directly to the Project Manager, depending on the project team structure.
⦁ .As a Junior Software Developer, you are responsible for successful completion of assigned development tasks.
Actively and permanently work on self-development and self-education, making lessons learned for further advancement to Middle position.
Improve your qualification within the area(s) of expertise at various training courses, seminars and/or other educational organizations.
Project Manager:
Is appointed by Program Manager, Department Manager.
Directly subordinates to Program Manager, Department Manager.
Junior Project Manager is working with multiple tasks within a project under supervision, can be managing an assignment of low complexity (maturity levels: Limited liability, Basic, Intermediate) in full
The role of the Junior Project Manager is to plan, execute and finalize projects according to strict deadlines and within budget under the direction of Project Manager, Senior Project Manager, Program Manager. The Junior Project Manager makes sure the project’s objectives are distinguished, oversees the completion of project tasks, monitors adherence to project management process standards, ensures quality control throughout the project life cycle.
click to edit
AREA RESPONSIBILITY DESCRIPTION
Project Management \ Integration Project documentation development Preparing and maintaining essential project documentation, such as project charter, PM plans, etc.
Project Management \ Integration Manage \ Control Project Execution Control the work being executed by the team, make sure the progress is as planned
Project Management \ Integration Learn domain Learn a project domain, use domain-specific vocabulary
Project Management \ Scope Managing \ Controlling Project Scope Define project scope and plan how it is to be managed, including change management
Project Management \ Scope Business Analysis \ Collecting Requirements Elicit requirements from a customer, apply various methods to fetch demands, requirements, feature acceptance criteria. Document/put requirements and priorities in specs, backlog, etc.
Project Management \ Scope Managing \ Controlling Requirements Making the process of effectively work with requirements, setting up the requirements lifecycle
Project Management \ Schedule Managing \ Controlling Project Schedule Plan and follow up on works progress, detect events impact on schedule, plan schedule and communicate updates to stakeholders
Project Management \ Budget Managing \ Controlling Project Budget Plan budget and its management procedures so that it is under control, all deviations are managed proactively
Project Management \ Budget Estimation works planning and coordination Planning and controlling works on preparation of estimates, preparation of a WBS
Project Management \ Quality Personal Engagement in Quality Control Participate and arrange internal demos, arrange usability reviews, etc. personally make sure the quality is according to requirements
Project Management \ Quality Control TEX and SEX Incorporate Valuable Engineering Practices Make sure TEX and SEX requirements and practices are in place, report about TEX and SEX statuses, make sure gaps (if any) are reasonable
Project Management \ Quality Identify and facilitate improvements continuously Detect gaps and issues, inefficiencies and prospects to improve in operational activities, introduce changes aimed at higher delivery efficiency, quality, and customer satisfaction
Project Management \ Quality Outline and collect lessons learned Identify project aspects and root causes the team (or company) can take a lesson from, so to use this knowledge in future projects. Collect these lessons in a structured form. Communicate about the lessons learned to company management or customer, follow up and ensure corresponding corrective and preventive actions are taken
Project Management \ Team Manage Team Ensure and keep track of team members' motivation, assess and influence team performance, manage team conflicts. Perform the role of People Manager
Project Management \ Communications Plan and Manage Communications Plan communications within and outside the team, define regular communications (reports, meetings) to ensure reasonable control, manage ad hoc communications to control customer's expectations
Project Management \ Communications Status Reporting Explicitly reflect the project status in a status report, follow company rules to fill in the status report's sections in ETS
Project Management \ Communications Presentations Holding presentations with customers (and other stakeholders) and within the company to share statuses, proposed methods of work, lessons learned, etc.
Project Management \ Risk Managing \ Controlling Project Risks Plan risk management procedures, identify, register, and follow up risks. Define the most appropriate response strategy and CAPA. Properly and proactively communicate risks \ issues.
Mentorship Prepare personal development roadmaps Review and make suggestions to mentees' personal development roadmaps, make appropriate suggestions to help them achieve their goals
TEX issues driven – issues that are connected with violations of applicable software development standards, bad technical decisions that are resulted in technical debt, refactoring efforts, etc.; TEX is strats after WO was sighned work order
SEX - security check
Intern
Intern is responsible for improving own skills and utilize them successfully on project tasks and getting Junior position within internship terms
Formulating ideas and facts in the written manner
Reporting on tasks fulfilled and providing status by request
Evaluating of tasks progressing and adjusting work style as needed
Dedicated and keen to keep the commitments
Identifying of problems that hinder the tasks implementation. Escalating problems with time-consuming resolution
click to edit
)
click to edit
click to edit
Earned value management:
Scope; Schedule; Resources measurement(project performance and progress)
Forecast - estimate at completion (EAC)
- estimate to completion (ETC)
TCPI - measure cost performance that is required to be achieved with the remaining resources in order to meet a specific management plan.
**
Project manage software -** ( Planned Value; Earned Value; Actual cost
Initialization(request for bit/proposal/information/ calls with customer/collect info/make scope/make proposal) -> If we won go to planning phase/ if we lost go to Initialization -> create project charter/ management plan/ risks register/Stakeholder register/ chose management and developing technical and human resources/create and validate plan of developing/deployment/testing/ and acceptance/ criteria of acceptance/ and other...-> has approved all docs and plans, then go to developing phase, If no go back to planning -> developing according to Scope, management plan, Change plan and others plans/Monitor if you manage your project according to Schedule/Time/Quality go to phase testing according to approved QA/QC strategy and approved docs with customer. If you have noticed problems then initiate Change request follow till the problem will be fixed -> Project was tested and all fine then go to close phase, if test shows that goals was not reached or customer not satisfied with results because product failed Dod and committed goals and other commitments then go back
Initation
Planning
Developing
Monitor and Control
Testing
Close
Estimation Techniques ![download]
click to edit
Dot voting is usually considered a decision-making tool, not an agile estimation technique.
effective way to prioritize or indicate the value of several small items quicklyThe more votes an item gets, the bigger its size, and the higher its priority.
High priority user stories are posted on the wall to receive the votes. This is done until the final order is achieved with the agreement of all stakeholders.
Since participants do not need to deliver a comparative judgment of each option, this method is quick and effective.
Out of the long litany of options available in the table, Dot Voting methodology leverages the collective wisdom of the team to ensure an increased focus on the most crucial issues of the project.
Planning Poker® is a consensus-based estimating technique.
If all estimators selected the same value, that becomes the estimate. If not, the estimators discuss their estimates. The high and low estimators should especially share their reasons
click to edit
I wanted to share an alternative estimating technique of T-shirt sizing instead of using Story points.
If you are used to the Fibonacci sequence for Story points you can think of the T-shirt sizes when you are estimating PBIs in a similar pattern — XS (1), S (2), M (3), L (5), XL (8). Eventually, the team can switch to using these points directly.
PERT Analysis
PERT Analysis
click to edit
Program Evaluation and Review Technique (PERT) is a method used to examine the tasks in a schedule and determine a Critical Path Method variation (CPM). It analyzes the time required to complete each task and its associated dependencies to determine the minimum time to complete a project.
click to edit
Definition Critical Path: The longest path of scheduled activities that must be met to execute a project.
Advantages: Provides Program Managers information to evaluate time and resources on a project. It helps give them the necessary information to make informed decisions and set a realistic schedule.
Disadvantages: The analysis can be highly subjective and be influenced a few outspoken team members. It also required a lot of time to continually update the analysis as a program progresses.
Earned value management (EVM)
click to edit
click to edit
Earned value management (EVM) is a project management methodology that integrates schedule, costs, and scope to measure project performance. Based on planned and actual values, EVM predicts the future and enables project managers to adjust accordingly.
click to edit
click to edit
Link to article with formulas
https://www.ecosys.net/knowledge/earned-value-management-basics/
click to edit
click to edit
Planned Value (PV)
PV = Total project cost * % of planned work
Actual Costs (AC)
However, it’s important to remember to include several hidden costs—material, resource, hardware, software licenses, overheads, etc.
Earned Value (EV)
At the end of 2 months, you may have planned to complete 40% of your work, but let’s say you managed to just finish 30%
In our example:
EV = Total project cost % of actual work = $25,000 30% = $7,500
Emails
The 4 U’s of writing headlines are:
Unique
Urgent
Useful
Ultra-specific (very specific)
Your email subject lines should definitely be useful and ultra-specific.
click to edit
Business emails are like letters. They have a format. This includes:
A salutation (a word or phrase like “Gentlemen,” “Dear Sir,” “Dear Madam” or “To Whom it May Concern” that is used to begin a letter)
An opening sentence
An ending
A closing
click to edit
Business emails are like letters. They have a format. This includes:
A salutation (a word or phrase like “Gentlemen,” “Dear Sir,” “Dear Madam” or “To Whom it May Concern” that is used to begin a letter)
An opening sentence
An ending
A closing
The language you use in each part adds to the email’s clarity and tone.
Salutation:
The salutation you choose changes depending on who your audience is. It helps set your email’s tone. Would you use “Hey” in the salutation of a formal email? Definitely not. Instead, you would start with “Dear” and the name of the person you’re writing to.
For example:
“Dear Sir or Madam” (if you don’t know the name of the person reading the email)
“Dear Mr. Smith”
“Dear Jim” (more informal)
Save “Hello,” “Hi” and “Hey” for when you want to create an informal tone.
What do you write when your email is going to a group of people? Some common salutations for groups are:
“Dear all” (more formal)
“Hi everyone” (more informal)
Opening Sentence:
Your opening sentence is the key to writing a clear email. A good opening sentence tells the reader what the email is about.
For example, if you’re writing to follow up on something, you could start with any of these:
“I’m just writing…”
“Just a (quick) note…”
“Just a short note to follow up on…”
What other words can you use to write a good opening sentence? Try these, followed with your reason for writing:
“I’m (just) writing to…”
“Just a (quick) note to…”
“Just a short email to…”
In business, people tend to write emails to:
Clarify something
Confirm something
Follow up on something
Let someone know about something
Answer a question
Ask a question
Thank someone for something
Update someone
One of the above will most likely be your reason for writing.
File Attachments:
If you’ve attached a file to your email, make sure you tell the person you’re writing to that you have attached it. The more specific you are, the better. Being specific adds to the clarity of the email. Here’s an example:
“I’m sending you this week’s schedule as an attachment.”
You can also start your sentence with:
“I’ve attached…”
“Please find attached…”
“I’m attaching…”
Ending:
When ending an email, ask yourself what you want the reader to do.
If you want them to reply to you, you can write:
“I look forward to hearing from you.” (formal)
“Looking forward to hearing from you.” (less formal)
“I look forward to your reply.” (formal)
“Hope to hear from you soon.” (informal)
If you want them to contact you if they need more information, you can write:
“Do not hesitate to contact me if you need any assistance.” (formal)
“Let me know if you need anything else.” (informal)
If you don’t want them to do anything:
“Thank you for your help/assistance.”
“Have a nice day/weekend.”
Closing:
Just like your salutation, your closing will depend on how well you know the reader. Common closings include:
“Sincerely” (formal)
“Kind/Best/Warm regards” (less formal)
You may have received emails with closings like these:
“All the best”
“Best”
“See you (soon)”
“Take care”
“Bye (for now)”
These closings help create a closer relationship when you already know your reader.
Below, you’ll find a guide that includes some specific language you can put in emails. For more ideas, check out the video “Writing a Business Email” on FluentU.
Business emails are like letters. They have a format. This includes:
A salutation (a word or phrase like “Gentlemen,” “Dear Sir,” “Dear Madam” or “To Whom it May Concern” that is used to begin a letter)
An opening sentence
An ending
A closing
The language you use in each part adds to the email’s clarity and tone.
Salutation:
The salutation you choose changes depending on who your audience is. It helps set your email’s tone. Would you use “Hey” in the salutation of a formal email? Definitely not. Instead, you would start with “Dear” and the name of the person you’re writing to.
For example:
“Dear Sir or Madam” (if you don’t know the name of the person reading the email)
“Dear Mr. Smith”
“Dear Jim” (more informal)
Save “Hello,” “Hi” and “Hey” for when you want to create an informal tone.
What do you write when your email is going to a group of people? Some common salutations for groups are:
“Dear all” (more formal)
“Hi everyone” (more informal)
Opening Sentence:
Your opening sentence is the key to writing a clear email. A good opening sentence tells the reader what the email is about.
For example, if you’re writing to follow up on something, you could start with any of these:
“I’m just writing…”
“Just a (quick) note…”
“Just a short note to follow up on…”
What other words can you use to write a good opening sentence? Try these, followed with your reason for writing:
“I’m (just) writing to…”
“Just a (quick) note to…”
“Just a short email to…”
In business, people tend to write emails to:
Clarify something
Confirm something
Follow up on something
Let someone know about something
Answer a question
Ask a question
Thank someone for something
Update someone
One of the above will most likely be your reason for writing.
File Attachments:
If you’ve attached a file to your email, make sure you tell the person you’re writing to that you have attached it. The more specific you are, the better. Being specific adds to the clarity of the email. Here’s an example:
“I’m sending you this week’s schedule as an attachment.”
You can also start your sentence with:
“I’ve attached…”
“Please find attached…”
“I’m attaching…”
Ending:
When ending an email, ask yourself what you want the reader to do.
If you want them to reply to you, you can write:
“I look forward to hearing from you.” (formal)
“Looking forward to hearing from you.” (less formal)
“I look forward to your reply.” (formal)
“Hope to hear from you soon.” (informal)
If you want them to contact you if they need more information, you can write:
“Do not hesitate to contact me if you need any assistance.” (formal)
“Let me know if you need anything else.” (informal)
If you don’t want them to do anything:
“Thank you for your help/assistance.”
“Have a nice day/weekend.”
Closing:
Just like your salutation, your closing will depend on how well you know the reader. Common closings include:
“Sincerely” (formal)
“Kind/Best/Warm regards” (less formal)
You may have received emails with closings like these:
“All the best”
“Best”
“See you (soon)”
“Take care”
“Bye (for now)”
These closings help create a closer relationship when you already know your reader.
Below, you’ll find a guide that includes some specific language you can put in emails. For more ideas, check out the video “Writing a Business Email” on FluentU.
click to edit
our business objectives;
the risks associated with our context and business objectives;
the needs and expectations of our Customers and other relevant interested parties;
the products and services we provide;
the complexity of processes we employ and their interactions;
the competence of persons within or working on behalf of our Company;
our size and organizational structure.
What is Quality?
Quality is meeting the requirement, expectation, and needs of the customer is free from the defects, lacks and substantial variants. There are standards needs to follow to satisfy the customer requirements.
Quality Assurance ensures that the approaches, techniques, methods and processes are designed for the projects are implemented correctly.
QC activities monitor and verify that the project deliverables meet the defined quality standards.
Quality Control is a reactive process and is detection in nature. It recognizes the defects. Quality Control has to complete after Quality Assurance.
click to edit
QA is the technique of managing quality. QC is a method to verify quality.
QA does not involve executing the program. QC always involves executing the program.
All team members are responsible for QA. Testing team is responsible for QC.
QA means Planning for doing a process. QC Means Action for executing the planned process.
Statistical Technique used on QA is known as Statistical Process Control (SPC.) Statistical Technique used on QC is known as Statistical Quality Control (SPC.)
QA is the process to create the deliverables. QC is the process to verify that deliverables.
click to edit
In QA, processes are planned to evade the defects
QC agreements with the discovery of the defects and modifying them while making the product
QA detects weakness
QC detects defects
QA is process oriented
QC is product oriented
QA is a failure prevention system
QC is a failure detection system.
The 5 Whys uses "counter-measures," rather than "solutions." A counter-measure is an action or set of actions that seeks to prevent the problem from arising again, while a solution may just seek to deal with the symptom. As such, counter-measures are more robust, and will more likely prevent the problem from recurring.
When to Use a 5 Whys Analysis
You can use 5 Whys for troubleshooting, quality improvement, and problem solving, but it is most effective when used to resolve simple or moderately difficult problems
click to edit
Tip 1:
The "5" in 5 Whys is really just a "rule of thumb ." In some cases, you may need to ask "Why?" a few more times before you get to the root of the problem.
In other cases, you may reach this point before you ask your fifth "Why?" If you do, make sure that you haven't stopped too soon, and that you're not simply accepting "knee-jerk" responses.
The important point is to stop asking "Why?" when you stop producing useful responses.
Tip 2:
As you work through your chain of questions, you may find that someone has failed to take a necessary action. The great thing about 5 Whys is that it prompts you to go further than just assigning blame, and to ask why that happened. This often points to organizational issues or areas where processes need to be improved.
Ishikava Diagram=Fishbone Diagrams
dentify the problem.
Work out the major factors involved.
Identify possible causes.
Analyze your diagram.
You'll find this method is particularly useful when you're trying to solve complicated problems.
Paretto
The vital few: A small number of sources that account for most of the problem.
The useful many: The large number of remaining sources that individually and collectively account for a relatively small part of the entire problem.
click to edit
The primary goal of using RCA is to analyze problems or events to identify:
What happened
How it happened
Why it happened…so that
Actions for preventing reoccurrence are developed