Introduction to leading

Technical lead vs Team lead vs Project coordinator

Technical Lead. Assumes main responsibility for the technical architecture vision, and steering technical work in that direction over time.

Team Lead. Assumes main responsibility for timely software delivery and the personal/professional development of team members.

Project Coordinator. It is light weight version of project manager, main responsibility for timely software delivery with acceptable quality, manage operational items in the project: vacations, team composition, rotation etc.

Project definition

A project is a temporary endeavor undertaken to create a unique product, service, or result.

The temporary nature of projects indicates that a project has a definite beginning and end.

Project phases

SDLC

Waterfall vs Agile

Waterfall vs Agile

Scrum

Kanban

Lean

QA and QC and TestingQuality AssuranceThe main responsibility of QA is to ensure that all processes and procedures are being performed and followed in the correct way.

Quality ControlEach build passes BVT (Build Verification Tests) to ensure that build is valid for testing:Core functionality is working and testableNew features are implemented correctlyReleased build has better quality than the previous one

TestingTest team performs different types of testing which are fully described in test plan

QA vs QCQuality Assurance Quality Control

Definition QA is a set of activities for ensuring quality in the processes by which products are developed.

QC is a set of activities for ensuring quality in products. The activities focus on identifying defects in the actual products produced.

Focus on QA aims to prevent defects with a focus on the process used to make the product. It is a proactive quality process.

QC aims to identify (and correct) defects in the finished product. Quality control, therefore, is a reactive process.

Responsibility !!!Everyone!!! on the team involved in developing the product is responsible for quality assurance

Quality control is usually the responsibility of a specific team that tests the product for defects.

Goal The goal of QA is to improve development and test processes so that defects do not arise when the product is being developed.

The goal of QC is to identify defects after a product is developed and before it's released.

Business analysis

Business analysis is a process of identifying business needs and determining solutions to business problems.

Strategic planning — to identify the organization's business needs

Business model analysis — to define the organization's policies and market approaches

Process design — to standardize the organization’s workflows

Systems analysis — the interpretation of business rules and requirements for technical systems (generally within IT) — to identify the organization's business needs

Business analysis: Team

Business Analyst (BA)

Requirements Analyst (RA)

System Analyst (SA)

People management

Risks Management: Risks

Risk is the potential of losing something of value, weighed against the potential to gain something of value. Values (such as physical health, social status, emotional well being or financial wealth) can be gained or lost when taking risk resulting from a given action, activity and/or inaction, foreseen or unforeseen. Risk can also be defined as the intentional interaction with uncertainty. 

Risk Management

Risk management is the identification, assessment, and prioritization of risks followed by coordinated and economical application of resources to minimize, monitor, and control the probability and/or impact of unfortunate events or to maximize the realization of opportunities.

Knowledge transfer and Knowledge management

Knowledge transfer (KT) is the practical problem of transferring knowledge from one part of the organization to another. Seeks to organize, create, capture or distribute knowledge and ensure its availability for future users.

Knowledge management (KM) is the process of capturing, developing, sharing, and effectively using organizational knowledge.

Knowledge transfer

• Identifying the knowledge holders within the organization

• Motivating them to share

• Designing a sharing mechanism to facilitate the transfer

• Executing the transfer plan

• Measuring to ensure the transfer

• Applying the knowledge transferred

• Monitoring and Evaluate

Knowledge transfer: Road mapFormal trainings and manual (up-to-date documentation)

Face to face: group• Boot camps• Workshops• Lessons learned session• Expert storytelling

Face to face: individual• Transitional trainings• Job shadowing• Peer mentoring

Multimedia• Knowledge maps• Library resources• Wiki pages

Customer expectationsCustomer Satisfaction == Meeting Expectations

Customer expectations management (CEM)

Customer expectations “S-M-I” approach

Communication scheme

Infrastructure

THANK YOU FOR YOUR ATTENTION!