Employee Competency Model

In today’s business world there are only two things you need to focus on: Developing clear strategies for your organization and implementing a
system that creates radical focus in the execution of those strategies!

The implementation of OKR Method then helps to set the right focus in the operative execution of the long term strategies. From there on it is
all about the people who make an organization: everybody needs to understand what big goal he/she contributes to with his/her daily work
and find meaning in this pursuit. We need strong values, healthy collaboration and a clear focus on the most important topics. After that come
lean processes and the efficient allocation of resources.

The elements of in4Velocity can be illustrated as follows:

2
Cognitive skills apply across all the skill areas, skills, and activities of in4Velocity. They are exhibited in the ability to apply knowledge and
reasoning while performing in4Velocity activities within technical skill areas. Competency levels for cognitive skills are not included in
in4Velocity, but cognitive skills become increasingly important at higher levels of technical competency because the scope and complexity of
work activities increases and expands as the levels of competency and related job assignments increase.

3
Behavioral attributes and skills are exhibited in the ability to productively apply knowledge, cognitive skills, and technical skills; they are not
unique to software engineering but allow software engineers to effectively contribute to desired outcomes.

4
5
Behavioural attributes and skills apply to all elements and at all levels of technical skill areas, skills, and activities. Behavioural attributes and
skills and cognitive skills are not specified by competency level; however, increasing competency in cognitive skills and behavioural attributes
and skills becomes more important as the levels of technical competencies, the scope of responsibilities, and the breadth of interactions
increase.

6
TECHNICAL SKILLS:

Life cycle skill areas are categorized by typical phases of software development and modification. In practice, software phases are often
intermixed, interleaved, and iterated in various ways; however, no implication of development processes (for example, predictive versus
adaptive) is intended.

The five life cycle skill areas and eight cross cutting skill areas are listed below respectively.

Life Cycle Skill Area Skill Sets

Software Requirement Skills Software Requirements Elicitation
Software Requirements Analysis
Software Requirements Specification
Software Requirements Verification and
Validation
Software Requirements Process and
Product Management

Software Design Skills Software Design Fundamentals

Software Design Strategies and Methods Software Architectural
Design
Software Design Quality Analysis and
Evaluation

7
Software Development Skills Software Development Planning
Managing Software Development
Detailed Design and Coding Debugging
Testing Integrating and Collaborating

Software Testing Skills Software Test Planning

Software Testing Infrastructure
Software Testing Techniques
Software Testing Measurement and
Defect Tracking

Software Sustainment Skills Software Transition

Software Support
Software Maintenance

8
Software Engineering Crosscutting Skill Areas

Crosscutting Skill Area Skills

Software Process and Life Cycle Skills Software Development Life Cycle Implementation
Process Definition and Tailoring Process Implementation
Management
Process Assessment and Improvement

Software Systems Engineering Skills System Development Life Cycle Modelling

Concept Definition System
Requirements Engineering System Design
Requirements Allocation Component
System Integration and Verification System Validation and
Deployment System Sustainment Planning

9
 Software Quality Skills Software Quality Management (SQM) Reviews (review, walkthrough,
inspection)
Audits (concentrate on both product
and process)

Software Security Skills Requirements

Design
Development
Testing
Process
Quality

Software Measurement Skills Plan Measurement Process

Perform Measurement Process

Category to be mapped in Skill Base system:

Mark if Criteria Sub‐Criteria below will be evaluated if “Criteria” is selected

to Be Evaluated Criteria
CATEGORY: COMMUNICATION
a Clearly exchanges ideas, messages and information both verbally and in writing.
b Actively listens to understand.
◻ Communication c Is generally understood and provides clear direction or expectations allowing others to deliver
the desired result.
d Is approachable; exhibits open and receptive verbal and non‐verbal communication.
a Proactively and respectfully deals with issues and concerns directly and honestly.
◻ Conflict Management b Values differences of opinion and work approaches.
c Manages and resolves conflicts and disagreements in a constructive manner; plans and takes
steps to prevent counter‐productive confrontations.
a Consistently and accurately exchanges information between appropriate teams
10
◻ Information Sharing b Appropriately keeps team members and/or management informed.
c Consistently maintains confidentiality and/or uses appropriate discretion.
CATEGORY: LEADERSHIP/MANAGEMENT
a Develops budget to achieve department goals and objectives.
◻ Budget Management b Manages resources to stay within budget and effectively responds to changing priorities.
c Adheres to internal processes and procedures.
a Knows when it is appropriate to delegate work.
◻ Delegation b Plans and assigns work to the appropriate person(s), providing for optimal performance.
c Provides support and directions, including clear expectations and timelines.
a Effectively leads through times of change; identifies opportunities associated with change.
b Professionally and effectively approaches conflict resolution.
c Builds consensus and commitment for achieving the organization's vision.
◻ Leadership d Motivates others; takes measurable steps to develop the mutual trust and respect necessary
for a productive, positive work environment.
e Serves as a role model by setting a personal example of what is expected.

11
Mark if Criteria To Sub‐Criteria below will be evaluated if “Criteria” is selected
Be Evaluated Criteria
a Provides developmental tools to team; encourages them to perform and contribute to the
organization by providing ongoing feedback and opportunities to learn through formal and
informal methods.
◻ People Management b Inspires and fosters team commitment, spirit, pride and trust. Facilitates cooperation and
motivates team members to accomplish group goals.
c Strategically plans workload of unit and assigns work to maximize skills and abilities of each
team member. Team is seen as responsive to the needs of the Company.
d Consistently selects best qualified candidates for positions; implements effective new hire
training to promote employee success.
a Regularly acknowledges a job well done.
◻ Recognition b Expresses confidence in people's abilities.
c Finds ways to celebrate accomplishments.
a Effectively identifies training needs and seeks appropriate resources and opportunities for skill
Training and development of self and Team.
◻ Professional Provides ongoing appraisal of an employee's work performance; addresses performance
Development b issues as they occur; provides regular and constructive performance evaluations in accordance
with the appropriate bargaining unit agreement or handbook.
c Creatively finds appropriate training resources and shows efficient use of resources.
CATEGORY: COMMITMENT TO THE COMPANY
Treats all employees fairly, equitably and without regard to legally protected categories [Race,
Equal Opportunity & a Sex, Veteran]
◻ Diversity Status, Color, National Origin, Sexual Orientation (including gender expression and identity),
Religion, Age, Marital Status, Disability, Creed and Genetic Information]
b Values and respects different cultures, backgrounds and orientations of others.
c Supports diversity related policies and initiatives and incorporates into work as appropriate.
a Actively involved with team and/or department; works with colleagues to improve
◻ Engagement performance within the job for the benefit of Company
b Exhibits commitment to and a positive attitude towards Company and its values.
12
 c Networks and builds positive relationships with colleagues.
a Exhibits and encourages creativity and is willing to experiment.
◻ Innovation b Challenges the status quo, supports change, and takes appropriate risks.
c Receptive to new ideas and collaborative problem solving.

13
Mark if Criteria Sub‐Criteria below will be evaluated if “Criteria” is selected
To Be Evaluated Criteria
a Has found ways to increase efficiency and effectiveness of Projects through the
◻ Leadership in incorporation of technology into work functions.
Technology / b Ensures efficient operations through the use of effective information systems.
Engineering c Leads by example, learning to use technology as appropriate to his/her duties.
Competency Matrix
a Demonstrates a working understanding of the rules, processes and regulations that govern
◻ Policy Compliance/ administrative functions.
Development b Follows established regulations and Company policies.
c Seeks and incorporates consultation from appropriate subject matter experts when needed.
d Seeks necessary change when policy/procedure/rules are non‐existent, obsolete, ineffective
or non‐compliant.
a Independently pursues a high level of performance and quality in Projects managed or
◻ Pursues Excellence provided.
b Anticipates and plans by regularly reviewing the need for change in the design and delivery
of Projects
c Consistently self‐evaluates to improve performance and identify opportunities for growth.
CATEGORY: PROFESSIONAL SKILLS
a Spends time to educate the customer as appropriate.
◻ Customer Service b Is considered approachable and courteous.
c Responsive to customer communications.
a Maintains knowledge and skills required for successfully carrying out job responsibilities.
◻ Job Responsibilities
B Applies most efficient and effective methods in completing job duties and responsibilities.
C Maintains knowledge of general profession trends.
a Decisions are considerate of past experiences; seeks appropriate input when uncommon
◻ Problem Analysis and situations arise.
Decision Making b Effectively analyses a problem and can develop a sound plan of action considering all
significant factors and stakeholders.
C Actively reflects upon completion and incorporates “lessons‐learned” into future processes.

14
15
Mark if Criteria To Sub‐Criteria below will be evaluated if “Criteria” is selected
Be Evaluated Criteria
a
Produces accurate, thorough, and reliable results/service.
◻ Quality of Work B
Provides complete and effective service to customers.
C
Documentation, files, reports and/or correspondence are clear, complete and accurate.
a
Identifies long and short term work priorities; work is organized and prioritized appropriately.
B
Assignments and projects are completed within specified time frame; deadlines are
◻ Productivity consistently met.
C Volume of work accomplished is appropriate.
D Delegates work when appropriate; consults with manager regarding department workload
management when necessary.
a Willingly adapts to changing circumstances.
◻ Versatility B Responsive to needs of department or work unit; possesses a variety of skills.
C Recognizes and evaluates how change impacts work and recommends/makes modifications.
CATEGORY: PERSONAL ATTRIBUTES/INTERPERSONAL SKILLS
Acceptance of a Open to receiving guidance from Manager.
◻ Supervision B Appropriately communicates with Manager when in disagreement or has concerns about
directives.
C Once decision has been made does his/her part to ensure that decision’s success.
a Demonstrates a commitment to assessment activities.
Professional B Carefully considers, plans, and executes assessment activities.
◻ Assessment C Selects assessment methods that are relevant and useful.
D Analyses assessment results and understands them within the context of established goals
and objectives.
E Utilizes results to monitor outcomes and informed decisions.
◻ Comprehension a Trusted to fully and completely carry out instructions.
B Takes the initiative to fully understand directives; seeks clarification as needed.
a Self‐assured, demonstrates faith in his/her ability to successfully complete a task.
◻ Confidence B Takes initiative and seeks guidance when appropriate.

16
 C Successfully completes tasks and handles situations within the scope of responsibility without
assistance or direct supervision.
a Manages time well and meets commitments; job attendance is reliable and meets
◻ Dependability expectations.
B Available and accessible as a resource for others.
C Remains effective under pressure.
D Keeps information organized and accessible to others.

Mark if Criteria to Sub‐Criteria below will be evaluated if “Criteria” is selected

Be Evaluated Criteria
a Interacts honestly and ethically with colleagues and other departments
b Uses appropriate discretion in communicating with others.
◻ Integrity c Maintains confidentiality as appropriate and is considered trustworthy.
d Is considered fair, someone who actively listens to all sides concerned; makes decisions only
after considering all the facts.
◻ Professional a Meets "reasonable person" standard for appropriate appearance, dress, and grooming.
Appearance b Overall appearance reflects positively on department and Company.
a Demonstrates a positive attitude about the job and the work environment.
◻ Professional Attitude b Attitude inspires co‐workers, fostering a positive work environment.
c Maintains composure and professionalism in stressful situations.
a Actively creates a plan of action to accomplish goals.
◻ Planning b Displays effective time management skills.
c Coordinates activities effectively with other departments
a Accountable for his/her own actions, decisions, and mistakes.
◻ Takes Responsibility b Is quick to identify when delays or errors have occurred; focuses on fixing the problem.
c Possesses the capacity to self‐assess and improve.

17
 a Demonstrates a high level of cooperation with team members; effectively problem‐solves as
◻ Teamwork part of the team.
b Maintains good working relationships with co‐workers to support a positive work environment.
c Empowers team members through encouragement and coaching.
d Recognizes the contributions of team members.

Detailed Description of the Activities to be performed by engineering department:

Strong Emphasis is on the below requirements for creating successful CoE ( Centre of Excellence)

IT Security Expert: Need of the Hour ( At least one CISSP or CISM certified person) Capable of conducting internal Audit on the
software Architecture, Infrastructure and Code Base on regular intervals. Impart complete Knowledge on the Standards to the
concern department

Compliance Percentage
Compliance Resolution – Number of unsettled cases of standards noncompliance for every thousand users
Compliance Cycle Time – Average number of days needed to prompt audit concerns into compliance
IT Security Support – Percentage of IT security problems settled within schedule
Total Expense: IT Security – The total cost incurred by the IT security office over a specific term
IT Security Cost per Supported Employee (Company Wide) – The expenses of IT security procedures for each companywide employee
Security Standards – Total number of yearly amendments to security guidelines
Percentage of System Downtime Related to Security Issue – The percentage of network, system, or application interruption that is
associated in particular to a security concern
IT Security Audits – Total number of yearly IT security checks
Employee per IT Security Audit – Number of agents needed for IT security checks for every thousand users
Maximum Encryption for Web Based Transactions – Maximum number of encryption levels devoted to online activities over a
specific term
Minimum Encryption for Web Based Transactions – Minimum number of encryption levels devoted to online activities over a specific
term
Corporate Data Encryption – Percentage of enterprise data encrypted for each level
Detection Systems – Percentage of network access points protected by breach detection systems

18
Intrusion Incidents Detected – Average percentage of breach cases immediately exposed by the breach detection systems
Cycle Time: Non Automatic Intrusion Resolution – The average number of minutes needed to address security issues that are not
immediately detected, from the time the breach happens until it is exposed
Virus Updates – Number of virus updates
Percentage of Systems Covered with Antivirus Software – Percentage of company owned computers that are presently carrying an up
to date antivirus application compared to the total number of computers owned by the firm.
Percentage of IT Security Issues Resolved on Time – The percentage of issues associated to IT security handled during a specific term
that were promptly completed
Compliance of Security Standards – Percentage of field improvement activities in conformity with enterprise security requirements at
the submission
Percentage of Customer Breach Claims
Passwords Required per User  – Average number of security codes needed per user

Project Management: Internal Project Management team ( At least one PMP certified Person)

Percentage of Projects Finished on Time – Percentage of projects associated with IT launched during a specified term that were
accomplished on schedule compared to the total number of projects
Percentage of Projects under Budget – Percentage of projects launched during a specified term that were accomplished without
budget review compared to the total number of projects
Projects Active per Project Manager – Total number of operative IT Projects over at a specific date divided by the total number of IT
project administrators
IT Project Cost Variance – The percent difference between projected and actual expenses for IT related Projects
IT Expense as a Percentage of Total Expense – Total expenditure by the IT office divided by the total, companywide operational costs
over the same term, as percentage
IT Expense per Employee

Quality Assurance: TL should be Certified QA Master

Defects per Product/Life Cycle – Average number of irregularities for every product life span
Internal Products Testing – Percentage of merchandise subjected to internal evaluation compared to the total number of
merchandise

19
Time Associated with Testing Process – Percentage of time spent on testing period compared to the total development time
Test Frequency – Number of evaluations authorized for other users
Number of Tests Performed by Test Lab Team – Total number of evaluations executed by the test lab team in a certain term
Test Lab Support/Maintenance – Human resources and expenses related to current test lab support and maintenance

Building Good, Intuitive & user Friendly Applications: General Interns

Ability to create web applications – Capacity to transform a highly technical procedure into a simple tool that can be utilized
efficiently by all with any level of technical knowhow
% of time spent fixing bugs – Total number of manhours consumed on resolving a glitch versus the number of manhours consumed
on developing new features
The ability of the developer to understand project requirements – Capacity to understand client specifications, product, and process
prerequisites
Understanding the full lifecycle of application development – Understanding the software/program cycle and the sequence in which
those stages are performed
Debugging ability – Capacity to detect and fix glitches promptly
Ability to create reusable modules – Efficient reuse of previous methods and producing reusable modules that can aid in time and
cost savings in subsequent projects

Delivering High Quality database scripts and optimization: Back end experts

Delivery of all requests on time – All requested queries if submitted on schedule time results in a better project results
Creativity in data storage and access – Capably normalize or denormalize according to the requirements of the project
The capability of troubleshooting common database issues – Capacity to employ an established methodology to determine and
repair performance issues in databases
Ability to optimize complicated SQL statements – Adept improving sizable and sophisticated SQL statements
Plan migration to Big data

Effective Defects and bugs Management: QA Engineers

20
Percentage of bugs detected by us verses the client – The percentage of errors or glitches found by quality assurance teams
compared to customers
Complete tasks within reasonable time – Successful completion of all duties designated within the specified time frame
Quality of bugs identified – A valuable testing procedure examines business philosophy followed by UI and then validations. This
metric assesses the nature of the detected errors.
Understanding of scope and clients business model – Testing is only as valuable as the understanding of the business design by the
tester. With an excellent understanding of the system goals, testing becomes useful and valid.

Effectively delivering projects within the stated scope and limit: Project Excellence

Ability to finish projects on time – Capacity to produce specific project milestones and complete the project within the specified
schedule.
Ability to finish projects on time – Capacity to produce specific project milestones and complete the project within the specified
schedule.
% of milestones missed – Percentage of components that did not satisfy the milestones in comparison to the components completed
on schedule.
Mentoring and implementation of best practices and processes – Capacity to coach the team and execute clearcut techniques

General Duties Expectations: For all the SDE

Ability to take responsibility for the allotted work – Being capable of working without supervision and the capacity to perform
efficiently
Communication ability that includes both verbal and written – Capacity to communicate in a confident and powerful way and the
ability to write clearly and in a concise manner
Effective listening skills – Capacity to actively interpret the knowledge imparted by the speaker and correctly receive and understand
messages
Compliance with documented process – Capacity to execute a series of steps or stages mentioned in the Process.
Email and internal communication efficiency – Timely and compelling replies to emails or Ryver messages
Ability to ask for assistance or questions at the right time – Effective working techniques where queries are asked promptly and help
is requested as necessary to conduct work

21
Team Management & Mentoring: Typically to all Team Leads

Group training hours spent per month – Number of hours consumed on a training session to lead a group toward a learning goal
Quality of process failure discussions – Efficiently discussing relevant points of issues or problems during training periods
Job satisfaction in the team – Number of Team members who are happy with their duties in the group
Managing project risks and change requests – Efficiently confront any incidents that might have an effect on the project’s outputs,
inputs, phases, or goals.
Process compliance in the team – Capacity to prompt people into compliance with predetermined processes Creativity and efficiency
index, usage of components and tools – Capacity to look for newer ways to minimize work and enhance quality by employing both
online and offline tools
Pre empting problems and timely execution – Preventing issues within projects and prompt completion of duties so that the work
proceeds seamlessly.
Preparing a second line leader – To cultivate other leaders and therefore establish organization potential for the present and the
future
Displaying Enthusiasm/Motivation/Creativity for assignment – A positive and passionate attitude for effectively performing tasks.

Test Management – Test Lead – QC T3

Ability to develop test strategy and execute it effectively – Capacity to assess and record all the primary duties and challenges of the
test project and perform it successfully.
Ability to complete testing for all contracted items within determined time – Capacity to understand the specifications of the project,
plan out activities, assignments and also accomplish within the specified time.
Ability to provide creative solutions to business problems – Capacity to view issues from an innovative mindset and recommend
original solutions
Quality of the test plan being executed – Efficiently prepare for specific goals, internal testing team and processes for a particular
beta test designed for software product

Evaluating System: PMS

Ability to examine system (Existing/new) – Capacity to evaluate current systems

22
Understanding & identifying client and system requirement – Capacity to interpret customer needs and system specifications and
collaborate with users to look for more requirements and innovations
Communication with team related to document creation or suggestions – Exceptional communication skills and recommendations
for process improvement
OKR Process Mapping and metrics evaluations

Team Lead Job Responsibilities: T3 – Technical Leads

Assure that the team members have the necessary education and training to effectively participate on the team.
Coach and help develop team members; help resolve dysfunctional behaviour.
Create an environment oriented to trust, open communication, creative thinking, and cohesive team effort.
Encourage creativity, risk taking, and constant improvement.
Ensure discussions and decisions lead toward closure.
Facilitate problem solving and collaboration.
Lead by setting a good example (role model) – behaviour consistent with words.
Maintain healthy group dynamics.
Motivate and inspire team members.
Provide team leadership and coaching.
Provide the team with a vision of the project objectives.
Recognize and celebrate team and team member accomplishments and exceptional performance.
Strive for team consensus and win-win agreements.

Software Developer Responsibilities: T1 Level

Determining operational practicality.

Developing quality assurance procedures.
Identifying areas for modification in existing Projects and subsequently developing these modifications.
Knowledge and interest in the latest technologies.
Researching, designing, implementing and managing software Projects.
Testing and evaluating new Projects.
The ability to communicate complex procedures to other colleagues.

23
The ability to learn new technologies quickly.
Training users.
Working closely with other developers, UX designers, business and systems analysts
Writing and implementing efficient code.

Office Policy Compliance:

Attendance and punctuality policy compliance. – An employee’s capability to be always on time and accomplish their designated
tasks on schedule.
Leave policy compliance. – Adherence to the firm’s attendance and punctuality guidelines which includes regularly arriving at the
office on time.
Process improvement initiatives. – Efforts to impart information and request policy amendments (Process ineffectiveness).
Personal presentation and grooming meet corporate standards. – Capacity of a Team member to be presentable in daily situations
which include positive characteristics such as confidence, verbal skills, personal appearance, and time management

Levels to define the Structure for all the engineering teams members:

Technology Job Function with six levels: T1T7.

T1: Very early career. Learning technical and professional skills. Interns
T2: Early career. Basic skills developed. Work contributes to success of team/product goals. SDE1 ( 2 to 4 years) Freshers
T3: Seasoned professional. Variety of technical skills developed. Strong problem solver. Key for success of team/product goals. SDE 2 (
Sr Software Engineers, Managers) ( 5 to 8 yrs.)
T4: Very senior. Can solve most problems or issues that arise. Uses experience to forward company goals/objectives. SDE3 ( PM,
Technical Lead) ( 10 to 15 yrs.)
T5: Exceptional. Considered expert/thought leader inside the company (and sometimes external as well). Drives
timeline/features/development through broad influence. SDE 4 ( Architect’s) ( 15 to 20 yrs.)
T6: Luminary. Very rare! Central to the company’s success. Translates organizational strategic goals into department/team plans.
Provides fundamental contributions to long term company planning in area of expertise. VP, AVP, Principal Architect ( 20+)

24
T7: Management Fellow ( CEO, CTO, CPO,CMO) ( 20+ years)

Key Designations can be as follows:

Chief Executive Officer - Co-Founder

Chief Technology Officer – Co-Founder
Chief Product Officer
Chief Marketing Officer
Vice President – Strategy & Innovation
Director – Engineering
Director – HR & Systems
GM – Product Management
Senior Project Manager / Senior Product Manager / Senior Software Architect
Project Manager / Product Manager / Software Architect
Project Lead / Senior Team Lead / Senior Technical Lead
Module Lead / Team Lead / Technical Lead
Senior Software Engineer / Senior QA Engineer
Software Engineer / QA Engineer

25
Agile Centre of Excellence in4Velocity

A premier organization providing an exceptional product in an assigned sphere of expertise and within a specific field of technology,
business, consistent with the unique requirements and capabilities of the CoE organization.

Why Setup a CoE??

There are several quantitative and qualitative benefits that can be reaped from a CoE:

26
Establish visibility and focus: Having a dedicated team means that employees and the world are aware of the focus. CoEs also
demonstrate that an organization is committed to excellence.
Eliminate Risks: CoEs are not impacted by the day to day business of an organization. They do not have to deal with immediate
revenue pressures and are free to channel their expertise and focus on a single business activity, process, or capability.
Flexibility: CoEs are not limited by all the process overheads that typical product teams may have to deal with. They have the
flexibility to innovate fast and fail fast.
Monitor Costs: CoEs make it easier to control and track costs. They help organizations measure KPIs and outcomes, especially around
RoI. They also help in planning and defining the focus areas for the future. 

No matter the size, the responsibilities of a LACE typically include:

Communicating the business need, urgency, and vision for change

Developing the implementation plan and managing the transformation backlog
Establishing the metrics
Conducting or sourcing training for executives, managers and leaders, development teams.
Facilitate Value Stream Identification Workshops and helping define and launch Agile Release Trains
Participating in critical, initial events like Program Increment (PI) Planning and Inspect and Adapt (I&A)
Fostering Best Practices from Agile Perspective
Communicating progress
Implementing Lean Agile focus days, with guest speakers, and presenting internal case studies
Benchmarking and connecting with the external community
Promoting continuing Lean Agile education
Extending Lean Agile practices to other areas of the company, including Lean Budgets, Lean Portfolio Management, contracts, and
human resources
Helping to establish relentless improvement (see Sustain and Improve in the roadmap)

27
What is the Role of the Leader in an Agile Transformation?

Leaders play a key role in the Agile Transformation. In many organizations, there is one key person who serves as the Agile
Transformation Leader. It is only with a solid understanding of this critical role that the transformation will succeed and deliver the
promised benefits.

Four Key Things Agile Leaders Do During an Agile Transformation – this includes establishing teams, shaping the environment,
coaching, and leading organizational change.
Establish High Performing Teams
Shape the Environment for Success
Coach
Leaders Lead Organizational Change

What Characteristics Do Agile Leaders Need

Growth Mindset
Self-Awareness
Ownership
Humility
Empathetic Listening Skills
Courage and Risk Taking
Trust
Ability to See & Optimize the Whole
Ability to Inspire Others

How Leaders May be the Impediment to Transformation

Action Steps for Agile Leaders

Last but not least

28
A company’s culture will trump any process changes, architectural changes, or organizational changes. If you’ve listened to any talks
on microservices, you will no doubt have heard about “Conway’s Law”, which states that “organizations which design systems … are
constrained to produce designs which are copies of the communication structures of these organizations.” So, even if we adopt agile
process, we have microservice architecture, and attempt to organize appropriately, we will still produce a system based on our
communicational structure, which is defined by the culture.

We need to be cognizant and proud of our heritage. We need to realize that this heritage will be driving a lot of our current
behaviours. In order to make effective change, we must first recognize what needs to be changed. If we get the culture right, then
anything is possible! Culture is like quality. You don’t build culture, or quality, by talking about it. You build it by doing things, by
acting, by making things happen and making things change, and reinforcing these actions patiently and continually over time, all the
time evolving it and improving to meet our needs.

29
Engineering Competency level Requirements: Key Attributes Mapping

Table 1
Software Requirements Skill Sets Software Requirements Activities

Identifies stakeholders for elicitation of requirements.

Engages stakeholders in elicitation of requirements.
Software Requirements Uses appropriate methods to capture requirements.
Elicitation Negotiates conflicts among stakeholders during elicitation.

Software Requirements Analysis Uses appropriate domain analysis techniques.

Performs analysis of requirements for feasibility and emergent properties.

Software Requirements Specification Uses appropriate notations for describing requirements.

Checks requirements for accuracy, lack of ambiguity, completeness, consistency, traceability,

and other desired attributes.
Software Requirements Verification and Validation Constructs and analyses prototypes.
Negotiates conflicts among stakeholders during verification.

Software Requirements Process and Product Uses appropriate methods for management of requirements, including configuration
Management management.

30
The following notations are used in Table: Follow (F), Assist (A), Perform (P), Lead (L), Create (C), Measure (M).

Table 2
Software Requirements Skill Sets and Activities by Competency Level
Levels

Skill Sets
Freshers T1 T2 T3 T4

1. Identifies important
Software stakeholders. (P/L)
Requirements
Elicitation
1. Assists in engaging 2. Engages different
different stake holders stakeholders to
to determine needs determine needs and
and requirements. (A) requirements. (P)

2. Assists in applying 3. Applies different

different methods to methods to the project
the project as appropriate to elicit
as appropriate to elicit requirements. (P)
requirements. (A)

31
Table 3
Software Requirements Skill Sets and Activities by Competency Level
Levels

Skill Sets Freshers T1 T2 T3 T4

1. Creates new ways to

Software 1. Selects appropriate engage and
Requirements 1. Assists requirements methods communicate with
Elicitation engineers with to engage and stake holders, the
preparation of surveys communicate with management team,
and other elicitation stake holders in and developers in
instruments. (F/A) requirements activities. requirements activities
(L) (C)

4. Assists in 2. Negotiates conflicts

negotiating conflicts between stake holders
between stake holders in requirements
in requirements elicitation. (P/L)
elicitation. (A)

32
 1. Leads identification
Software of emergent properties
Requirements 1. Selects the most and requirements
Analysis appropriate domain throughout the soft 1. Creates new domain
1. Assists analysis methods. (P/L) ware development life analysis methods. (C)
in domain cycle. (P)
analysis. (A)

Table 4
Software Requirements Skill Sets and Activities by Competency Level
Levels

Skill Sets Freshers T1 T2 T3 T4

1. Selects the most
Software 1. Reviews specifications 1. Reviews specifications appropriate formal and 1. Creates new
Requirements of requirements for of requirements for informal requirements requirements validation
Verification and errors and omissions. errors and omissions. (L) validation and and verification
Validation (P) verification techniques. techniques. (C)
(L)

2. Assists in prototype 2. Creates prototypes of

Development and different types as
testing. (F/A) needed. (P)

33
 3. Assists in negotiating 2. Negotiates conflicts
conflicts between stake between stake holders
holders in requirements in requirements
verification. (A) verification. (P/L)

1. Sets strategy and

Software 1. Follows and applies direction for the
Requirements defined processes for 1. Assists in applying 1. Performs tradeoff requirements process
Process requirements defined processes for analysis of requirements across projects and
Management engineering with requirements activities. (P/L) functional units of an
guidance. (F/A) engineering. (A) organization. (L)

Software Design Skills:

Table A12
Software Design Skill Sets Software Design Activities

Employ enabling techniques (such as abstraction, coupling/cohesion, information

hiding, and so forth) in software design.
Apply exception handling and fault tolerance techniques in software design.
Software Design Fundamentals Use restructuring and refactoring methods in software design.
Apply, as appropriate, design techniques in the areas of concurrency, event
handling, data persistence, or distributed software.

34
 Determine the process and strategy to be used in software design (such as top down
or bottom up, stepwise refinement, use of patterns and pattern languages, iterative
and incremental processes, and so forth).
Select and apply the appropriate design methodology (such as a structural or object
Software Design Strategies and Methods oriented approach).
Consider design alternatives and perform trade off analysis.
Manage software design activities.

Use architectural styles, views, models, and patterns to specify the high level
organization of a software system.
Software Architectural Design Specify the component interfaces.
Design software components and modules using models, design patterns, notations,
and diagramming techniques.

Utilize software design reviews.

Perform static analysis tasks to evaluate design quality.
Software Design Quality Analysis and Develop and use simulation and prototypes to evaluate software design quality.
Evaluation Manage requirements change.

The following notations are used in Table: Follow (F), Assist (A), Perform (P), Lead (L), Create (C).

Table 5
Software Design Skill Sets and Activities by Competency Level
Levels

Skill Sets
Freshers T1 T2 T3 T4

35
 1. Assists 1. Applies enabling
Software Design software techniques (such as 1. Analyzes
Fundamentals designers 1. Assists in the abstraction, coupling/ 1. Evaluates the and makes
with tools application of enabling cohesion, information effectiveness of the recommendation
and tech techniques in the design hiding, and so forth) to application of software
niques for of software the design of software design enabling related to
gathering components and components and techniques. (P/L) organiza
information modules. (A) modules. (P) tionwide
about appli application
cation and of software
use of soft design fun
ware design damentals.
fundamen (C)
tals. (F/A)
2. As appropriate in
2. Assists the domain of applica 2. Provides
in the tion, applies appropri direction
application ate design techniques in and advice
of design the areas of concur on methods
techniques rency, event handling, and tech
in the areas data per sistence, or niques to
of concur distributed software. (P) be used in
rency, event the areas
handling, of concur
data per rency, event
sistence, or handling, or
distributed distributed
software. software.
(A) (L)

36
Table 6
Software Design Skill Sets and Activities by Competency Level
Levels

Skill Sets
Freshers T1 T2 T3 T4

3. Assists 3. Applies
Software in the appli exception
Design cation of handling
Fundamentals exception and fault
handling tolerance
and fault techniques
tolerance in the
techniques design of
in the software
design of components
software and mod
components ules. (P)
and mod
ules. (A)

37
4. Assists 4. Uses restructuring
in the use and refactoring
of restruc methods in the design
turing and of software
refactoring components and
methods in modules. (P)
the design
of software
components
and mod
ules. (A)

38
Table 7
Software Design Skill Sets and Activities by Competency Level
Levels

Skill Sets Freshers T1 T2 T3 T4

1. Provides 1. Determines
Software assistance the pro
Design in the 1. Assists in the applica cess and
Strategies and installation tion of the designated 1. Applies the desig strategy to
Methods and use of software design strategy nated software design be used in 1. Examines and
tools appro and methodology to strategy and meth software assesses the effec
priate for create a software design odology to create a design at tiveness, across an
a project’s (such as an incremental software design (such as the project organization, of the
designated object-oriented an incremental level (such application of software
design approach). (A/P) object-oriented as topdown design strategies and
strategy approach). (P) or bottom methods. (M)
and meth up, step
odology wise refine
(such as an ment, use
incremen of patterns
tal object and pattern
oriented languages,
approach). iterative
(F/A) and incre
mental pro
cesses, and
so forth).
(L)

39
2. Selects 2. Analyzes
the appro and makes
priate recom
design mendations
methodol related to
ogy (such organiza
as object tionwide
oriented, software
function design
oriented, strategies
component and meth
based) and odologies.
strategies (M)
to be used
at the proj
ect level.
(L)

40
Table 8
Software Design Skill Sets and Activities by Competency Level
Levels

Skill Sets
Freshers T1 T2 T3 T4

3. Provides
Software guidance
Design and advice
Strategies and on the use
Methods of software
design
strategies
and meth
ods. (L)
4. Evaluates
the effec 3. Creates new tech
tiveness of niques evaluating
the applica software design quality.
tion of the (M)
selected
software
design
methodol
ogy. (P/L)
2. Determines 5. Determines design
design alternatives and
alterna

41
tives and performs trade off
performs analysis. (L)
Trade off
analysis.
(P/L)

42
Table 9
Software Design Skill Sets and Activities by Competency Level
Levels

Skill Sets Freshers T1 T2 T3 T4

1. Applies
Software standard
Architectural notations,
Design diagram
ming tech 1. Analyzes
niques, and makes recom
1. Assists in architec models, and 1. Provides direction mendations related to
tural design tasks asso patterns and advice on standard organization wide
ciated with use of stan (such as notations, diagramming software architectural
1. Provides assistance in dard notations, architectural styles, tech niques, models, design. (M)
the installation and use diagramming structural and behav and patterns to be
of software architecture techniques, ioral models, structured applied. (L)
tools. (F/A) models, and patterns. systems
(A) design
models,
and UML) to
model the
High level
organization
of a soft
ware sys
tem. (P/L)

43
2. Applies 2. Creates 2. Determines
a selected multiple 2. Evaluates the effec new meth
software views of the tiveness of the creation ods and
design pat software of software architec techniques
tern to the system. ture. (P/L) to be used
design of (P/L) in archi
a software tectural
component design. (M)
or module.
(A/P)

44
Table 10
Software Design Skill Sets and Activities by Competency Level
Levels

Skill Sets Freshers T1 T2 T3 T4

Software 3. Uses design pat terns
Architectural and frameworks to
Design design midlevel software
components or modules.
(P)
1. Selects appropriate
Software Design tools and techniques
Quality Analysis 1. Assists software (such as design reviews, 1. Analyzes and makes
and Evaluation designers with tools and static analysis, simulation recommendations
techniques for collecting and prototyping, design related to organiza
design 1. Facilitates software metrics) tionwide design quality
metrics and evaluating 1. Participates in design reviews. (P/L) to ensure a software evaluation and analysis
software design qual ity. software design reviews. design’s quality. (L) techniques. (M)
(F/A) (P)
2. Carries out static 2. Leads static analysis
analysis tasks to evaluate tasks
design qual ity. (P) to evaluate design qual
ity. (P/L)

45
Table 11
Software Design Skill Sets and Activities by Competency Level
Levels

Skill Sets Freshers T1 T2 T3 T4

3. Assists 3. Develops and uses
Software Design in develop simulation and pro
Quality Analysis ment and totypes to evaluate
and Evaluation use of sim software design qual ity.
ulation and (P)
prototypes
to evaluate
software
design qual
ity. (A)

46
2. Uses the
results of
software
design
quality 2. Creates new tech
evaluation niques for evaluating
activities software design quality.
to assess (M)
the qual
ity of the
design and
to decide
on correc
tive action,
if needed.
(P/L)
3. Provides
guidance
and direc
tion related
to the need
for require
ments
change
resulting
from design
review.
(P/L)

47
Software Development Skills: The following notations are used in Table: Follow (F), Assist (A), Perform (P), Lead (L), Create (C).

Table 12
Software Development Skill Sets Software Development Activities
Select appropriate processes and models for constructing software, including appropriate
reuse processes.
Software Development Planning Select appropriate languages and tools for
software Development.
Select appropriate frameworks, platforms, and
environments.
Establish and follow project standards for version control and configuration management.
Managing Software Collect and monitor standard measures of
Development code quality and size.
Create detailed designs that minimize complexity and enhance quality.
Create code to implement detailed designs.
Refactor code when needed.
Establish and follow standards for designs and
Detailed Design and Coding code.
Use appropriate design patterns.
Use defensive coding techniques to minimize propagation of errors and threats.
Document code through comments to support
software maintenance.
Generate code from design models.
Use appropriate tools and techniques for debugging.
Create and execute unit tests for all delivered
Debugging and Testing code.
Achieve test coverage goals.

48
 Establish and follow integration strategy and
processes.
Integrating and Collaborating Perform integration testing as part of the integration process.
Collaborate with other team members in development activities (such as pair
programming, informal reviews).
Participate or lead reviews and inspections.

Table 13
Software Development Skill Sets and Activities by Competency Level
Levels

Skill Sets Freshers T1 T2 T3 T4

49
 1. Assists in 1. Selects
Software the selec appropriate
Development tion of processes
Planning appropriate and models
processes for con 1. Creates or proposes
and models structing new processes and
for software software on models for software
construc individual construction. (C)
tion. (F/P) projects
(such as
compilation,
genera
tion from
domain
specific
languages).
(L)
2. Assists in 2. Creates
the selec new lan
tion of guages and
appropriate tools for
languages software
and tools construc
for software tion. (C)
construc
tion. (F/P)

50
Table 14
Software Development Skill Sets and Activities by Competency Level
Levels

Skill Sets Freshers T1 T2 T3 T4

3. Assists in
Software the selec 2. Selects appropriate
Development tion of languages and tools for 3. Creates or proposes
Planning appropri software construction new frame works, plat
ate frame on individual projects. forms, and environ
works, (L) ments. (C)
platforms,
and envi
ronments
for software
construc
tion. (F/P)
3. Selects
appropri
ate frame
works, plat
forms, and
environ
ments for
individual
projects. (L)

51
 1. Assists in 1. Uses standard tools 1. Monitors 1. Establishes 1. Establishes
Managing the instal and processes for standard project organization
Software lation of version control and measures of standards standards
Development tools and configura tion man code quality for version for version
repositories agement. (P) and size. (P) control and control and
for version configura configura
control and tion man tion man
configura agement. agement.
tion man (L) (L)
agement.
(A)
2. Collects 2. Sets organization
standard standards for code
measures of quality and size. (L)
code quality
and size. (P)

52
53
Table 15
Software Development Skill Sets and Activities by Competency Level
Levels

Skill Sets

54
 Freshers T1 T2 T3 T4
3. Creates new tools and
Managing processes for version
Software control and configuration
Development management. (C)

1. Assists in the 1. Creates and reviews

Detailed Design installation of tools and 1. Creates code to detailed designs and 1. Measures and 1. Establishes
and Coding repositories for design implement detailed code that meet quality monitors an organization standards
and coding. (A) designs. (P) requirements. (P) organization’s use of for detailed designs and
design pat terns. (L) code. (L)

2. Suggests and per

forms appropriate code 2. Creates new design
2. Refactors code when refactoring when patterns. (C)
needed. (P) needed. (L)

3. Follows project and 3. Selects or establishes

organization standards project standards for
for designs and code. (F) designs and code. (P)

4. Uses appropriate 4. Suggests and uses

design pat terns. (P) appropriate design pat
terns. (L)

55
Table 16
Software Development Skill Sets and Activities by Competency Level
Levels

Skill Sets Freshers T1 T2 T3 T4

5. Uses defensive coding 5. Suggests and uses

Detailed Design techniques to minimize defensive coding
and Coding propagation of errors techniques to minimize
and threats. (P) propagation of errors
and threats. (L)

6. Documents code
through comments to
support software
maintenance. (P)

7. Generates code and 6. Writes executable 2. Plans and initiates

systems from mod els models suitable for code model driven develop
(such as UML) as generation as ment processes as
appropriate. appropriate. (P/L) appropriate.
(P) (L)

56
Table 17
Software Development Skill Sets and Activities by Competency Level
Levels

Skill Sets Freshers T1 T2 T3 T4

1. Assists in the installa 1. Uses appropriate 1. Ensures project 1. Establishes project
Debugging and tion of tools for debug tools and techniques standards for unit test standards for unit test 1. Establishes
Testing ging and testing. (A) for debugging. (P) coverage are followed. coverage. (L) organization standards
(P) for unit testing. (L)

2. Creates and exe 2. Selects appropriate

cutes unit tests for all debugging tools and 2. Creates new unit
delivered code. (P) techniques for a proj testing tools and meth
ect. (L) ods. (C)

3. Achieves test cover

age goals set by proj
ect and organization
standards. (P)

57
 1. Follows project 1. Assists in selection of 1. Establishes
Integrating and 1. Assists in installation integration strategy 1. Leads code reviews project tools and organization standards
Collaborating of integration tools. (A) and processes. (P) and inspections. (L) processes for integra for integration tools
tion. (P) and processes. (L)

2. Assists in creation of 2. Performs integration 2.

code inspection testing as part of the Establishes
packages. (A) integration process. (P) organization standards
for reviews and inspec
tions. (L)

58
Table 18
Software Development Skill Sets and Activities by Competency Level
Levels

Skill Sets Freshers T1 T2 T3 T4

3. Collaborates
Integrating and with other 3. Creates new inte
Collaborating team mem gration tools and
3. Assists in scheduling bers in development processes. (C)
code inspections. (A) activities (such as pair
programming,
informal
reviews).
(P)

4. Participates 4. Creates
in project new code
defined review and

59
 reviews and inspection
inspections. methods.
(P) (C)
4. Sets up
Build and
install environments
where the
software
packages
can be integrated. (P)

Software Testing Skills:

Table 18
Software Testing Skill Sets Software Testing Activities
Identify all stakeholders involved in software testing.
Identify success and failure criteria.
Identify test completion criteria.
Software Test Planning Design and implement the software test plan.
Identify and coordinate customer representatives and other stakeholders participating
in the software acceptance and/ or demonstration.

60
 Identify tools to be used throughout testing
activities.
Software Testing Infrastructure Identify appropriate documentation to be generated and archived.
Design/select and implement the test
environment.
Identify test objectives.
Software Testing Techniques Select appropriate testing/demonstration techniques.
Design, implement, and execute test cases.
Identify, collect, and store appropriate data resulting from testing/demonstration.
Report test results to appropriate stakeholders.
Software Testing Measurement and Defect Identify, assign, and perform necessary
Tracking corrective actions.
Analyze test data for test coverage, test
effectiveness, and process improvement.

Table 19
Software Testing Skill Sets and Activities by Competency Level
Levels

Skill Sets Freshers T1 T2 T3 T4

1. Identifies 1. Identifies 1. Establishes 1. Establishes

Software Test unit and stakehold organiza organiza
Planning integration ers par tional pro tional pro
testing suc ticipating cedures for cedures for
cess and in dem testing. (P) testing. (L)
failure crite onstration
ria. (P) and testing
activities.
(P)

61
 2. Designs 2. Identifies
and imple customer
ments a representa
software tives and
2. Follows test plan. other stake
software (P) holders
test plan. participat
(P) ing in the
acceptance
testing and
demonstra
tions. (L)

62
Table 20
Software Testing Skill Sets and Activities by Competency Level
Levels

Skill Sets Freshers T1 T2 T3 T4

63
 3. Establishes the
Software Test criteria for unit test
Planning execution completion, 3. Identifies success
such as code cover age, and failure criteria for 3. Identifies project test
defect intensity, and so test ing. (L/P) objectives. (L)
forth. (P)
4. Identifies success
4. Develops demon and failure criteria for
4. Develops unit test stration or other test system and acceptance
plan. (P) plans. (P) testing. (P)
5. Assists with the 5. Establishes criteria 5. Identifies test com
development of the for demonstration readi pletion criteria. (P)
test plan. ness. (A/P)
6. Selects the most
appropriate demonstra
tion, testing technique.
(P)

64
Table 21
Software Testing Skill Sets and Activities by Competency Level
Levels

Skill Sets Freshers T1 T2 T3 T4

7. Establishes the crite
Software Test ria for test comple
Planning tion, such as defect
arrival
rate, defect intensity,
and so forth. (P)
8. Establishes criteria
for regression testing,
such as defect density
and so forth. (P/L)
1. Identifies organiza
Software 1. Sets up the neces 1. Defines the neces 1. Identifies testing tional testing tools and
Testing sary test and dem 1. Selects appropriate sary setup for testing tools and test data data warehousing
Infrastructure onstration environ unit test techniques. and dem onstration. ware housing across across projects. (L)
ment. (P) (P/L) projects. (P)

65
 2. Creates new test
2. Identifies the appro documentation
2. Installs the neces 2. Selects the most priate docu (in other words, test
sary tools. (P) appropriate testing mentations necessary plan, defect record
tools. (P) for the testing activi ing, and so forth). (L/P)
ties. (P)

66
Table 22
Software Testing Skill Sets and Activities by Competency Level
Levels

Skill Sets Freshers T1 T2 T3 T4

67
Software 3. Develops the appro 3. Designs and imple 3. Designs the test
Testing priate infra structure for ments the test envi environment. (L/P)
Infrastructure data warehous ing. (P) ronment. (P)
1. Performs manual test 1. Specifies appropriate 1. Creates new testing
Software activities (in other test cases for the (in other words, unit,
Testing words, data entry, test 1. Designs and exe cutes selected testing 1. Designs system test integration,
Techniques case execution, and so unit test cases. (P) technique. (L/P) plan and test cases. (L) stress, and so forth)
forth). (P) techniques. (C)
2. Assists with the 2. Identifies automated
2. Executes regression development of the test testing opportunities.
testing. (P) cases. (P) (L/P)
3. During demonstra
tion, monitors cus
tomer use and records 3. Executes integration
customer feedback for and system test cases.
product improvement. (P)
(A)

Table 23
Software Testing Skill Sets and Activities by Competency Level
Levels

Skill Sets Freshers T1 T2 T3 T4

4. Ensures the system is
Software ready for demon
Testing stration by performing 2. Executes test cases.
Techniques acceptance test. (P/L) (L/P)
3. Develops automated
test case scenarios. (L/P)

68
 1. Performs all appro
Software priate
Testing data ware housing 1. Collects appropriate 1. Collects appropriate
Measurement (gathering execution data associated with data associated with 1. Conducts root cause 1. Creates new root
and Defect data, data entry, data test execution. (P) test execution. (L/P) analysis. (L/P) cause analysis tech
Tracking archiving, and so forth). niques. (P)
(P)
2. Generates appropri 2. Evaluates test execu 2. Analyzes test data to
ate reports associated tion results and identi decide on further
with test / demonstra fies appropriate rework. 2. Conducts root cause testing activities. (L)
tion execution. (P) (P) analysis. (P)

69
Table 24
Software Testing Skill Sets and Activities by Competency Level
Levels

Skill Sets Freshers T1 T2 T3 T4

3. Monitors test prog

Software 3. Collects ress by evaluating defect 3. Using the
Testing appropriate arrival rate, failure test results, 3. Uses
Measurement data associ intensity, and so forth. assigns the data to
and Defect ated with (A/P) appropriate evaluate
Tracking executing rework to test effec
test cases. team mem tiveness. (L)
(P) bers. (P)

4. Uses
test execu
tion data 4. Evaluates test results
and rework to identify appropri ate
4. Provides results process improvement
test result to evalu opportunities. (P)
report to ate test
appropriate effective
Stake hold ness and
ers. (P) decide for
additional

70
testing or
regression
testing. (P)
5. Monitors 5. Monitors
test prog overall test
ress by progress
evaluat by evaluat
ing defect ing defect
arrival arrival
rate, failure rate, failure
intensity, intensity,
and so and so
forth. (P) forth. (L)

71
Software Sustainment Skills:

Table 25
Software Sustainment Skill Sets Software Sustainment Activities
Develops transition plan.
Identifies stakeholders for transition and operational requirements.
Identifies system and software constraints.
Identifies applicable systems and software operational standards (such as information
assurance).
Develops software transition and operational
documentation.
Software Transition Installs software.
Performs software operational training (for
both users and sustainment personnel).
Determines the impacts on the operational
environment.

72
 Develops software system activation and checkout procedures.
Participates in system acceptance.
Maintains current software configurations.
Performs operational software assurance.
Updates COTS and other software technologies to maintain currency.
Diagnoses and responds to reported software defects, anomalies, and operational incidents
Software Support and events.
Monitors system operation and collects
operational data.
Develops and implements software retirement
procedures.
Establishes software maintenance processes and plans.
Obtains and maintains baseline software
artifacts.
Performs problem identification and technical impact analysis.
Makes and assures changes to software (corrective, adaptive, perfective).
Software Maintenance Performs preventative maintenance and
software reengineering.
Monitors and analyses software maintenance
activities.

73
74
Table 26
Software Sustainment Skill Sets and Activities by Competency Level
Levels

Skill Sets Freshers T1 T2 T3 T4

1. Participates 1. Modifies existing and

Software in develop 1. Leads development creates new guidelines
Transition ing transi of transition plans. (L) for transition plans. (C)
tion plans.
(P)

2. Participates 2. Leads in 2. Modifies

in the iden the identi existing
tification of fication of and creates
stakehold stakehold new guide
ers for tran ers for tran lines for
sition and sition and the identi
operational operational fication of
require require stakehold
ments. (P) ments. (L) ers. (C)
3. Participates 3. Leads in
in the iden the identi
tification of fication of
system and system and
software software
constraints. constraints.
(P) (L)

75
4. Identifies 4. Modifies
applicable existing and
systems develops
and soft new sys
ware opera tems and
tional stan software
dards. (P) operational
standards.
(L)

76
Table 27
Software Sustainment Skill Sets and Activities by Competency Level
Levels

Skill Sets Freshers T1 T2 T3 T4

1. Assists in identifying 5. Leads in the devel

Software applicable systems and opment of software 5. Approves software
Transition software operational transition and opera transition and opera
stan dards. (A) tional documentation. tional documentation.
(L) (L)

77
 2. Assists in the devel
1. Follows instructions opment of software 3. Modifies existing and
to help develop transition and opera creates new templates
software transition and tional docu mentation. for software transition
operational docu (A) 6. Leads in the installa 6. Approves new and operational docu
mentation. (F) tion of software. (L) software installations. mentation. (C)
Installs software. (P) (L)

3. Assists in the devel

opment of training 7. Develops training 7. Approves training
2. Follows instructions material for operational material for operational material for operational
to help install software. support personnel. (A) support personnel. (P) support personnel. (L)
(F)

3. Assists in training 4. Trains software

operational support operational support 8. Leads software
personnel. (A) personnel. (P) operational training. (L)

Table 28
Software Sustainment Skill Sets and Activities by Competency Level
Levels

78
Skill Sets Freshers T1 T2 T3 T4
5. Performs software 9. Develops software 8. Approves software
Software system activation and system activation and system activation and
Transition checkout procedures. checkout procedures. checkout procedures.
(P) (P) (L)
4. Modifies existing and
10. Participates in deter creates new guidelines
6. Assists in mining the impacts of 9. Leads in determining for deter mining the
determining the software changes on the impacts of software impacts of software
impacts of software the operational envi changes on the opera changes on the opera
changes on the opera ronment. (P) tional environment. (L) tional environment. (C)
tional environment. (A)
5. Modifies existing and
develops new system
7. Assists in system 11. Participates in 10. Leads system acceptance methods,
acceptance. system acceptance. (P) acceptance. (L) tools, and techniques.
(A) (C)

79
80
Table 29
Software Sustainment Skill Sets and Activities by Competency Level
Levels

Skill Sets Freshers T1 T2 T3 T4

1. Modifies existing and
Software creates new standards
Support 1. Operates operational 1. Performs operational 1. Develops operational 1. Approves operational and frame works for
software configuration software configuration software configuration software configuration operational software
management tools. (A) management. (P) management plans. (L) man agement plans. (L) configuration man
agement. (C)

2. Follows instructions 2. Leads operational

to perform operational 2. Performs operational software assurance 2. Develops software
software assurance software assurance. (P) activities. (L) assurance plans. (L)
tasks. (F)
3. Updates COTS and 3. Leads maintenance
3. Installs COTS and other software tech of COTS and other
other software nologies to maintain software technologies
updates. (P) currency. (P) to maintain currency.
(L)
4. Diagnoses and
responds
to reported software 4. Leads software help 3. Creates policies that
defects, anomalies, and desk activities. (L) 4. Develops software cover help desk opera
operational incidents help desk plans. (L) tions. (C)
and events. (P)

81
Table 30
Software Sustainment Skill Sets and Activities by Competency Level
Levels

Skill Sets Freshers T1 T2 T3 T4

82
 2. Modifies existing and
Software creates new methods,
Support 5. Operates tools to 5. Acquires tools and 4. Develops plans for tools, and techniques
collect operational data 5. Analyzes operational supervises analysis of collecting and for collecting and
under supervision. (F) data. (P) operational data. (L) processing operational processing operational
data. (L) data. (C)

6. Assists in 6. Implements software

implementing software retirement procedures. 5. Develops software
retirement procedures. (P) retirement plans. (L)
(A)

1. Modifies existing and

Software 1. Assists in 1. Leads development creates new software
Maintenance implementing software 1. Implements software of software maintenance policies,
maintenance processes maintenance processes maintenance processes processes, and
and plans. (A) and plans. (P) and plans. (L) procedures. (C)

1. Participates in 2. Obtains and

obtaining baseline maintains software 2. Identifies software
software artifacts. (P) baseline artifacts. (P) baseline artifacts. (L)

83
Table 31
Software Sustainment Skill Sets and Activities by Competency Level
Levels

Skill Sets Freshers T1 T2 T3 T4

2. Leads problem
Software 3. Performs problem 3. Performs change identification and
Maintenance identification. (P) impact analysis. (P) techni cal impact
analysis. (P)
3. Leads develop ment 2. Modifies existing
4. of plans and supervises and creates new
4. Assists in making Implements plans and making changes to policies and
changes to software makes changes to software (corrective, procedures for making
(corrective, adaptive, software (corrective, adaptive, perfective). changes to software
perfective). (A) adaptive, perfective). (L) (corrective, adaptive,
(P) perfective). (C)
4. Plans for and 3. Modifies existing
2. Assists in performing 5. Performs preventa 5. Leads preventative supervises preventa and creates new
preventative mainte tive maintenance and maintenance and tive maintenance and policies and
nance and software software software software procedures for preven
re-engineering re-engineering re-engineering re-engineering tative main tenance
activities. (A) activities. (P) activities. (L) activities. (L) and software
re-engineering. (C)
6. Assists in monitoring 6. Monitors and ana 5. Leads monitoring
and analyz ing software lyzes software main and analysis of
tenance activities. (P)

84
maintenance activ software maintenance
ities. (A) activ ities. (L)

85
Software Process Life cycle

Table 32
Software Process and Life Cycle Skill Sets Software Process and Life Cycle Activities

Determine one or more organization wide life cycle models (Agile)

Select a team software process (plan driven,
adaptive).
Software Development Life Cycle Lead a small team in execution of some portion of a life cycle process model (such as
Implementation software design).
Carry out process activities specified in a life cycle process model script.

Define software processes for a project team or for a software engineering activity (such
as requirements engineering).
Tailor a defined software process to the needs of a project team or software
Process Definition and Tailoring engineering activity.
Interpret and adapt a software process to individual process responsibilities and tasks.
Lead definition and tailoring of organization
wide software processes.

Implement and execute software processes.

Provide guidance and advice to software teams on how to implement and manage
Process Implementation and Management software processes.
Serve as a member of a software engineering process group.

86
 Collect data for assessment of a software process.
Analyze process assessment data and implement
Process Assessment and Improvement improvement of team software processes.
Use assessment information and reports for
software process improvement.

87
Table 33
Software Process and Life Cycle Skill Sets and Activities by Competency Level

Levels

Skill Sets Freshers T1 T2 T3 T4

1. Provides 1. Leads a
Software assistance 1. Carries out process small team 1. Determines the
Development in the activities specified in execution 1. Selects a life cycle need for and selects or
Life Cycle installation in a life cycle process of some model process for a develops an organi
Implementatio and use of model script. (A/P) portion of software team. (L) zation wide life cycle
n tools appro a life cycle model. (C)
priate for process
a project’s model (such
designated as software
life cycle design).
model. (F/A) (P/L)
2. Assists 2. Selects
in selec depart
tion of a ment or
department organiza
or organiza tionwide
tionalwide process
life cycle models. (C)
process
model. (P/L)
3. Advises
on process
infrastruc
ture, train
ing, and
tools. (C)

Table 34

88
Software Process and Life Cycle Skill Sets and Activities by Competency Level

Levels

Skill Sets Freshers T1 T2 T3 T4

1. Leads definition and 1. Conducts

Process tailoring of software research
Definition and processes for a project into effec
Tailoring 1. Provides 1. team or for a software tive soft
assistance Interprets and adapts a engineering activity ware
in the software process to 1. Provides review of (such as requirements process
installation individual process defined and tailored engineering, design, and definition
and use of responsibilities and processes. (A/P) so forth). (L/C) and tailor
tools for tasks. (A/P) ing. (C)
defining and
modifying
software
processes.
(F/A)

2. Provides guidance to 2. Leads definition and

2. Tailors others involved tailoring of organization
a software in tailored processes wide software
process to (individual and team). processes. (L/C)
the work (L)
of a small

89
 team. (P/L)

Table 35
Software Process and Life Cycle Skill Sets and Activities by Competency Level

Levels

Skill Sets Freshers T1 T2 T3 T4

1. Provides assistance
Process in the installation and 1. Leads large teams or 1. Provides organiza
Implementatio use of tools for 1. Leads small teams in multi team projects in tion wide guidance and
n and implement ing, man 1. Collaborates in the the implementation the implementation advice on how to
Management aging, and measuring execution and execution of a and execution of a implement and
software processes. of a team software software process. (P/L) software process. (L) manage software
(F/A) process. processes. (C)

2. Provides guidance
and advice to indi 2. Provides guidance
viduals on the imple and advice to software
2. Implements and mentation and man teams on how to
man ages individual agement of their implement and
processes. (F/A) personal processes. manage software
(P/L) processes. (L/C)

90
3. Serves as a member 2. Provides guidance
of a software engineer and advice on the for
ing pro cess group 3. Serves as leader of mation, structure, and
(SEPG). (P) an SEPG. (L) responsibilities of
SEPGs. (C)

91
Table 36
Software Process and Life Cycle Skill Sets and Activities by Competency Level
Levels

Skill Sets Freshers T1 T2 T3 T4

1. Provides assistance in 1. Conducts research
Process the installation and use 1. Leads small teams in 1. Leads software teams into the effective ness
Assessment and of tools for assessing 1. Assists in collecting collect ing data for in collecting data for and improvement of
Improvement and improving software data for assessment assessment of software assessment of software software processes. (C)
processes. (F/A) of a software processes. (P/L) processes. (P/L)
process. (A)
2. Analyzes process 2. Analyzes process
assessment data and assessment data and
2. Collects data relevant implements improve implements improve
to individual process ment of small team ment of team software
execution. (F/A) software processes. processes. (P/L)
(P/L)

92
Table 37
Software Systems Engineering Skill Sets Software Systems Engineering Activities

Select and integrate a software engineering development model into a system

System Development Life Cycle Modeling engineering development model.
Tailor policies, procedures, and templates and 2. Uses assessment data,
select applicable standards. 3. Leads the SEPG in team reports, and SEPG
3. Assesses
Identifyand implestakeholders.
system providing guidance on reports to establish
ments improvement
Develop of 3. Asconcepts
the operational a member of an context,
(system department or organiza
operational organization procedures
environment(s),
Concept Definition an individual software
prioritized features, SEPG,
qualitypro vides input
attributes, on tion wide
operational software
scenarios, and standards for
assumptions,
process. (A/P)
dependencies, software
limitations, andprocess
exclusions). process improvement. software process
improvement. (A/P) (L/C) improvement. (C)

93
 ]

Identify system level traceability requirements

System Requirements Engineering and tools.
Identify system requirements.
Develop the system requirements specification.
Develop plans, procedures, and scenarios for system integration, verification,
validation, and deployment.
Develop alternative solution concepts.
Identify system components and specify relationships and interfaces among
components.
Conduct trade studies to identify major system components for hardware/software/
System Design manual operations.
Participate in making acquisition decisions for system components.
Influence system design to avoid isolated
stovepipe units of software.
Allocate requirements and interfaces to system components (functional, behavioral,
structural, quality) and interfaces between software components and other major
system components.
Develop bidirectional traceability between system requirements and software
Requirements Allocation requirements.
Analyze, clarify, and refine requirements
allocated to software.
Determine needed kinds of software components (database, algorithms, internet
protocols).
Make acquisition decisions for software components (buy, build, open source, and
so forth).
Component Engineering Work with software engineers who develop and integrate software components.
Provide liaison from software engineering to systems engineering and other major
component engineering.

94
 Integrate software with other system
System Integration and Verification components.
Participate in system verification activities.
Provide liaison to software component engineers.
System Validation and Deployment Participate in simulated and live system tests.
Participate in system acceptance testing.
Provide liaison to software component engineers.
Participate in planning for system sustainment.
System Sustainment Planning Prepare for operational support.
Provide liaison and participate in planning for
software sustainment.

95
Table 38
Software Systems Engineering Skill Sets and Activities by Competency Level

Levels

Skill Sets Freshers T1 T2 T3 T4

1. Uses tools and 1. Assists in integrating 1. Participates in
System follows directions to the selected software integrating the 1. Prepares
Development prepared depictions development model selected software 1. Participates in frameworks for
Life Cycle and documentation of into the systems development model selection of the system integrating an orga
Modeling tailored development development model. into the system development nization’s system and
models. (F) (A) development model. life cycle model. (P) software develop ment
(P) models. (C)

2. Leads selection of
the soft
ware development
life cycle model. (L)

96
 3. Leads
System integration
Development of the soft
Life Cycle ware devel
Modeling opment
model into
the sys
tem devel
opment
model. (L)
2. Participates
in systems 4. Participates in/leads 2. Modifies
engineering tailoring existing
meetings of policies, procedures, models and
and pre and templates, and creates new
pares meet selection of applicable models and
ing minutes standards for projects ways of
to include and programs. (P/L) integrated
decisions software
made, open engineering
issues, and system
other rel engineering
evant dis develop
cussions, ment mod
and action els. (C)
items. (A)

97
 3. Determines
System applicable policies,
Development procedures, standards,
Life Cycle and guide lines and
Modelling tailors them for an
organization’s system
and software
development models.
(C)
1. Identifies potential
Concept stakeholders by
Definition examining historical
data and having discus
sions with appropriate 1. Develops lists of
1. Assists by locating personnel inside and stakeholders and 1. Prepares criteria for 1. Develops new tech
identified stake hold outside the systems categorizes their likely identifying stake hold niques for identifying
ers. (A) engineering team. interests. (P/L) ers. (L) stakeholders. (C)
(A/P)

98
Table 39
Software Systems Engineering Skill Sets and Activities by Competency Level
Levels

Skill Sets Freshers T1 T2 T3 T4

Concept 2. Attends stakeholder
Definition meetings and solicits
2. Arranges stakeholder stakeholder needs, 2. Leads stakeholder
meetings. (A) wants, and desires. (P) meetings. (L)
2. Attends stakeholder
3. Attends stakeholder meetings to document
meetings and takes stakeholder needs,
meeting minutes. (A) wants, and desires. (P)
4. Follows directions to 3. Leads development of 2. Develops new meth
prepare elements of the 3. Develops elements of scenarios, story boards, 3. Facilitates ods, tools, and tech
Concept of Operations. the Concept of prototypes, and use development of the niques for concept
(F) Operations. (A) cases. (L) Concept of Operations. definition. (C)
(L)

99
 4. Obtains stakeholder
consensus on the
Concept of Operations.
(L)
5. Develops acceptance
criteria. (P)

Table 40
Software Systems Engineering Skill Sets and Activities by Competency Level

Levels

Skill Sets Freshers T1 T2 T3 T4

1. Attends meetings and
System documents the system 1. Establishes the system 1. Establishes the system 1. Establishes organi
Requirements development envi development envi development envi zational policies and
Engineering ronment and technology ronment and identfies ronment and identifies procedures for system
con straints. (P) technology constraints. technology constraints. requirements engi
(P) (L) neering. (P)

2. Modifies existing and

2. Procures and operates develops new methods,
trace ability tools to 1. Provides training on 2. Identifies system level 2. Identifies system level tools, and techniques for
establish and maintain traceability procedures trace ability require trace ability require system requirements
trace ability. (P) and tools. (A) ments and tools. (P) ments and tools. (L) engineering. (C)

100
 3. Follows instructions to 2. Assists in develop 3. Participates in develop 3. Leads development of
document the system ment of the system ment of the system require
requirement specifica require the system requirements ments spec
tion. (F) ments spec specification. (P) ification. (L)
ification. (A)

Table 41
Software Systems Engineering Skill Sets and Activities by Competency Level
Levels

Skill Sets Freshers T1 T2 T3 T4

101
 3. Assists in devel 4. Participates in devel 4. Leads the devel
System 4. Documents plans, pro opment of plans, proce opment opment of plans, proce
Requirements cedures, and scenarios dures, and scenarios for of plans, procedures, dures, and scenarios for
Engineering for system integration, system integration, and scenarios for system system integration,
verification, validation, verification, validation, integration, verification, verification, validation,
and deployment. (A) and deployment. (A) validation, and deploy and deployment. (L)
ment. (P)
1. Assists in developing 1. Participates in develop
System Design alternative solution ing alternative solution 1. Leads development of
concepts and con concepts and con alternative solution 1. Develops policies and
ducting trade stud ies to ducting trade stud ies to concepts to identify procedures for system
identify major system identify major system major sys design in an organiza
components. (A) compo nents. (P) tem compo tion. (C)
nents. (L)
2. Participates in identify
ing system compo nents 2. Leads/ participates in
2. Participates in making as well as the interfaces making buy/build
buy/build decisions for and relationships among decisions for major
software components. components. (P) system components.
(P) (L/P)

3. Recom
System Design 3. Assists mends buy/ 3. Approves
in selecting build deci buy/build
components sions for decisions
to be pro software for soft
cured. (A) compo ware. (L)
nents. (P)
1. Identifies
sources of 4. Procures selected
software software components. (L

102
components
to be pro
cured. (A)
5. Participates 4. Leads/ participates in 2. Develops new
in system system design meetings approaches to system
design to avoid isolated stove design to avoid isolated
meetings to pipe units of software. stove pipe units of
avoid iso (P/L) software. (C)
lated stove
pipe units
of software.
(P)

103
Table 42
Software Systems Engineering Skill Sets and Activities by Competency Level
Levels

Skill Sets Freshers T1 T2 T3 T4

1. Identifies 1. Leads/ 1. Develops
Requirements allocable participates new meth
Allocation 1. Documents and non in meetings ods, tools,
allocable allocable to identify and tech
and non require and allocate niques for
allocable 1. Assists in identifying ments. (P) require require
require allocable and ments ments allo
ments. (F) non-allocable require (functional, cation and
ments. (A) behavioral, flowdown.
structural, (C)
quality) and
interfaces
to software
components
and other
major sys
tem compo
nents. (L/P)

104
 2. Attends meetings
2. Documents and records minutes 2. Participates in
allocation to allocate require meetings to allocate
of require ments (functional, requirements
ments behavioral, structural, (functional, behavioral,
(functional, quality) and interfaces structural, quality) and
behavioral, to software interfaces to software
structural, components and other components and other
quality) and major system compo major system compo
interfaces nents. (P/L) nents. (P)
to software
components
and other
major sys
tem compo
nents. (F)

105
Table 43
Software Systems Engineering Skill Sets and Activities by Competency Level

106
 Levels

Skill Sets Freshers T1 T2 T3 T4

3. Participates in 3. Leads meetings to
Requirements meetings to refine refine requirements
Allocation requirements allocated allocated to software.
to software. (P) (L)
3. Develops bi direc
tional traceability 4. Leads traceability
3. Operates traceability between system from system require
tools and generates requirements and ments to software
traceability reports. (F) software require requirements. (L)
ments. (P)
4. Assists in clarifying 4. Participates in 5. Leads in clarifying
and refining require clarifying and refining and refining require
ments allocated to requirements allocated ments allocated to
software. (A) to software. (P) software. (L)
1. Assists in deter 1. Leads in determining 1. Modifies existing and
Component mining and document needed kinds of develops new meth
Engineering ing needed kinds of 1. Determines needed software components ods, tools, and tech
software components. software components. for a project or niques for component
(A) (P) program. (L) engineering. (C)

107
Table 44
Software Systems Engineering Skill Sets and Activities by Competency Level
Levels

Skill Sets Freshers T1 T2 T3 T4

2. Assists in determining 2. Leads the buy/build
Component 1. Documents buy/build buy/build decisions for 2. Determines buy/build decision making process
Engineering decisions for software software components. (L) decisions for software for software compo
components. (A) components. (P) nents. (L)

108
 3. Develops and inte 3. Develops and inte 3. Establishes procedures
2. Maintains grates software com grates software com to develop and integrate
baselines of software ponents. (A/P) ponents. (P/L) software components. (L)
components. (A)
4. Provides liaison from
software engineering to
systems engineering and
other major component
engineering. (L)

1. Modifies existing and

System pro vides new methods
Integration 1. Assists in integration of 1. Assists in system 1. Participates in integra 1. Leads integration of of integrating software
and Verification software with other verification activities. (A) tion of software with software with other with other system compo
system components. (A) other system compo system components. (L) nents. (C)
nents. (P)

2. Leads/ participates in
System 2. Participates in system system verification
Integration and verification activities. (P) activities. (L/P)
Verification

2. Assists in providing 3. Leads/ participates in

liaison to software 3. Provides liaison to providing liaison to
component engineers. software component software component
(A) engineers. (P) engineers. (L)

109
 1. Modifies existing and
System develops new methods,
Validation and 1. Operates tools for 1. Assists in performing 1. Participates in simu 1. Leads/ participates in tools, and techniques for
Deployment performing simulated simulated and live system lated and live system simulated and live system system validation and
and live system tests. (F) tests. (A) tests. (P) tests. (P/L) deployment. (C)

2. Operates tools for

performing system 2. Assists in system 2. Participates in system 2. Establishes system
acceptance testing. (F) acceptance testing. (A) acceptance testing. (P) acceptance criteria. (L)

110
Table 45
Software Systems Engineering Skill Sets and Activities by Competency Level
Levels

Skill Sets Freshers T1 T2 T3 T4

3. Serves as liaison to
System software component
Validation and engineers during system 3. Leads/ participates in
Deployment validation and system acceptance
deployment. (P) testing. (P/L)
4. Leads in providing
liaison
to software component
engineers during sys
tem validation and
deployment. (P/L)
1. Participates in
System identifying stake
Sustainment 1. Assists in planning for holders and developing 1. Establishes criteria
Planning system sustainment. (A) a transition plan and and procedures for
requirements for system sustainment.
operational support. (P)
2. Leads/ participates in
2. Prepares for opera planning for system
tional support. (P) sustainment. (L)

Software Quality Skills:

111
Table 46

Software Quality Skill Sets Software Quality Activities

Instill a culture of producing high quality products.

Establish and follow quality goals and quality attributes.
Establish and follow a quality plan.
Identify, establish, follow, and verify appropriate processes, standards, and quality models that
facilitate achieving quality goals and attributes.
Identify stakeholders that have authority and/ or accountability for the process and product
quality.
Identify and use appropriate tools and measurements needed to reach quality goals and
Software Quality Management (SQM) attributes.
Establish and execute corrective actions if quality goals are not achieved.
Establish and execute appropriate continuous
improvement processes.
Establish and update requirement traceability metrics and verification metrics.

112
 Plan, organize, and conduct appropriate review meetings.
Participate as a member of the review team.
Reviews (review, walkthrough, inspection) Collect and analyze appropriate data resulting
from the review.
Identify, assign, and perform necessary
corrective actions.

Plan, organize, and conduct independent audits.

Audits (concentrate on both product and process, Collect appropriate data resulting from the
but are done by an independent, internal or audit.
external, organization) Collect and analyze data collected from the
audits.
Establish and implement appropriate
resolutions for identified problems.

113
 Identify and collect a set of quality data under
statistical control.
Identify a set of subjective and objective
Statistical Control variances for the data.
Analyze collected data.
Establish and implement a set of control processes.
Evaluate the effectiveness of the control processes.

The following notations are used in Table: Follow (F), Assist (A), Perform (P), Lead (L), Create (C).

Table
Software Quality Skill Sets and Activities by Competency Level
Levels

Skill Sets Freshers T1 T2 T3 T4

114
 1. Establishes a culture 1. Creates new and
Software Quality 1. Follows quality of producing quality improved quality
Management 1. Follows defined quality standards for the 1. Establishes quality products and of following practices for delivering
(SQM) processes and standards. product and supporting standards for the quality processes across high quality products.
(P) processes. (P) product. (P/L) projects. (P/L) (C)

2. Assists with establishing

the appropriate
infrastructure (such as 2. Selects appropriate
defect tracking tools) to SQM processes that
support organizations’ 2. Follows defined support the identified 2. Creates new
quality goals. (A) quality models. (P) quality goals for the processes. (C)
project. (P)

3. Identifies quality 3. Examines and

3. Uses appropriate characteristics and 2. Establishes quality assesses the
tools and resources to attributes for the standards, models, and effectiveness of a
develop quality product and establishes processes for projects. specific SQM process
products. (P) priorities. (P) (P/L) across an organization.
(C)

115
Table
Software Quality Skill Sets and Activities by Competency Level
Levels

Skill Sets Freshers T1 T2 T3 T4

3. Analyses the
Software Quality advantages and
Management 4. Assists with identification 4. Identifies the quality disadvantages of
(SQM) of the different quality models that need to be alternative SQM 4. Makes
characteristics and followed for the project. processes and tools recommendations
attributes for the product. (P) that can be used for related to organization
(A/P) achieving wide SQM processes. (C)
organizational goals
for product quality.
(P)
5. Develops the Quality 5. Creates/ modifies SQM
5. Ensures that product Assurance (QA) plan for the 4. Develops the QA processes to achieve
quality goals are achieved. project. (P) plan for the project. higher quality products
(P) (L) and pro cesses. (C)
6. Identifies appropriate
6. Collects quality metrics stake holders who have 5. Identifies
and prepares quality authority and account organizational 6. Proposes/ Designs new
documentation to be ability regarding the quality measures that tools
shared with appropriate process and quality support achieving to improve the
stakeholders. (P) product. (P) product quality goals achievement of product
quality goals. (L)

116
 (across projects).
(P/L)

7. Develops and updates an 7. Identifies appropriate

Software Quality appropriate traceability measures that support 6. Identifies
Management matrix for the product. (P) achieving product quality continuous
(SQM) goals. (P/L) improvement
opportunities across
projects. (L)

8. Identifies appropriate
tools and resources that
need to be used in order
to achieve product quality
goals. (P/L)

9. Verifies that quality

goals and requirements are
met. (P/L)

10. Identifies continuous

improvement opportuni
ties across the project. (L)

117
Table
Software Quality Skill Sets and Activities by Competency Level
Levels

Skill Sets Freshers T1 T2 T3 T4

Assists with necessary
Reviews logistics associated with
reviews and inspections,
including but not limited
to:
meeting logistics, (P)
,and

118
 generating appropriate 1. Participates as an 1. Identifies appropriate 1. Identifies appropriate 1. Creates new or
reports associated with active member of the review processes needed organization wide review customizes review pro
the meeting. (P) review team in order to to achieve product processes. (P/L) cesses to meet orga
achieve the goals of the quality goals. (P/L) nizational needs. (C)
activity. (P)
2. Identifies appropriate 2. Conducts across the
2. Uses appropriate personnel that need to organization data analy
checklists called for by participate in review sis for the purpose of 2. Develops new root
the review organizer. (P) activities. (P) root cause analysis. (P) cause analysis tech
niques. (C)

3. Based
Reviews on the
review data,
3. Collects appropriate 3. Identifies appropriate identifies appropriate
and accurate data that is measures that need to corrective actions to be
called for by the review be collected as part of implemented across proj
organizer. (P) the product review. (P) ects for the purpose
of achieving product
improvement ( P/L)
4. Produces 4. Identifies appropriate
appropri artifacts under the
ate docu review and correspond
mentation ing check list. (P)
called for by
the quality
manage
ment plan.
(P)
5. Analyzes collected
5. Follows product data for the

119
 appropriate purpose of root cause
practices analysis and assessment
defined by of review effective ness.
the quality (P)
manage
ment plan.
(P)

Table
Software Quality Skill Sets and Activities by Competency Level
Levels

Skill Sets Freshers T1 T2 T3 T4

120
 6. Identifies appropriate
Reviews corrective actions in
order
to achieve product
improvement. (P)
7. Leads the review team.
(P)
Establishes audit infra
Audits structure by identifying:
appropriate organization
to conduct the audit, (P)
products and processes
that need to be included
in audits, (P) and
1. Establishes the environ stake holders receiving
ment necessary to 1. Plans, organizes, and the audit results. (P) 1. Creates new audit
conduct the audit. (A/P) 1. Participates in audits. conducts processes. (C)
(P) audits. (P/L)

2. Analyzes audit results

Audits 2. Classifies issues iden for continuously improve
tified by audits. (P) ment. (P)
3. Establishes and imple
ments appropriate
resolution strategies for
identified issues. (P)
1. Establishes the envi 1. Creates or modifies
Statistical ronment necessary for 1. Collects a set of quality 1. Identifies a set of organizational statistical
Control data col lection and data under statistical con 1. Analyzes the collected quality data under sta qual ity control gates. (C)
warehous ing. (P) trol. (P) data. (L) tistical control. (P)

121
 2. Identifies a set of
subjective and objective
2. Deploys a set of variances for the data. (P)
control processes. (P)
3. Evaluates the effec
tiveness of the control 3. Analyzes the collected
processes. (A) data. (L)
4. Establishes
Statistical and imple
Control ments a set
of control
processes.
(P)
5. Evaluates
the effec
tiveness of
the control
processes.
(P)

122
Software Security Skills Area:

Table
Software Security Skill Sets Software Security Activities

Identify security risks (such as misuse cases).

Requirements Create requirements that capture security
issues.
Perform initial threat modeling.
Model threats and associated risks of new and modified systems.
Identify the attack surface of new and modified systems.
Design Follow recommended design principles to create secure systems.
Use appropriate, secure design patterns.

Follow recommended secure coding principles to avoid security vulnerabilities (such as

buffer overflow, input validation).
Development Follow recommended coding standards to avoid security vulnerabilities.

Process Collect and monitor metrics for security

assessment processes.
Perform code reviews to identify security
Quality vulnerabilities.
Use static analysis methods to identify security vulnerabilities.

123
The following notations are used in Table : Follow (F), Assist (A), Perform (P), Lead (L), Create (C).

Table
Software Security Skill Sets and Activities by Competency Level
Levels

Skill Sets Freshers T1 T2 T3 T4

1. Creates or proposes
Requirements 1. Identifies security new meth ods for
risks (such as misuse recognizing security
cases). (P) vulnerability . (C)

2. Creates require
ments that capture
security issues. (P)

3. Performs initial
threat modeling. (P)

124
 1. Follows
Design recom
mended
design
principles
to create
secure sys 1. Models
tems (such threats and
as provid associated
ing multiple risks of new
layers of and modi
protec fied sys
tion, using tems. (P)
access con
trol mecha
nisms, and
encrypting
sensitive

125
 data). (F)
2. Identifies
the attack
surface
(in other
2. Uses appropriate, words, the areas of
secure design pat terns. potential weakness
(F) exploited by attackers)

of new and
modified
systems.
(P)

Table
Software Security Skill Sets and Activities by Competency Level
Levels

Skill Sets Freshers T1 T2 T3 T4

126
 1. Follows 1. Establishes
Development recom organiza
mended 1. Selects or establishes tion coding
secure cod project coding standards standards 1. Creates new coding
ing prin to avoid security to avoid standards to avoid
ciples to vulnerabilities. (P) security security vulnerabilities.
avoid secu vulnerabili (C)
rity vulner ties. (L)
abilities
(such as
buffer over
flow, input
validation).
(F)

127
2. Follows
recom
mended
coding
standards
to avoid
security 2. Reviews and approves
vulner coding standards to
abilities avoid security
(such as vulnerabilities. (P)
validating
input and
preventing
exception
handling
mecha
nisms from
revealing
too much
information
about appli
cations and
systems).
(F)

128
 1. Assists 1. Follows 1. Establishes
Process in the col project organization standards
lection of standards for security assessment
metrics for in the col processes. (L)
security lection of
assessment security
processes. assessment
(A) metrics. (F)
1. Assists in 1. Performs code 1. Selects
Quality the instal reviews appropriate 1. Creates new static
lation of to identify security static analy analysis methods or
static analy vulnerabilities. (P) sis tools tools. (C)
sis tools. to identify
(A) security
vulnerabili
ties. (P/L)
2. Uses
static analy
sis methods
to identify
security
vulnerabili
ties. (P)

Software Safety Skills Sets:

Table
Software Safety Skill Sets Software Safety Activities

129
 Conduct formal system hazard analyses.
Identify safety requirements and verify their
Requirements completeness.
Assure that safety requirements are correct and realizable.
Propose and select design solutions to assure the hazards are mitigated.
Analyze design risk from a safety perspective.
Design Verify completeness and correctness of the design from a safety perspective.
Ensure safety requirements are met.
Select project coding standards to assure code safety.
Implement code components and their interfaces, considering safe coding practices to
Development avoid safety violations.
Verify that the safety aspects of a design are
implemented in the produced code.
Perform testing to assure safety requirements
are met.
Testing Use industry guidelines and established organization standards for safety validation and
verification.
Use established organization standards for safety assessment and selection of safety
criteria.
Process Identify artifacts required to establish a safety
case.
Use industry criteria to verify the completeness of the safety requirements.
Collect data and report about the safety
aspects of the product and process.
Quality Analyze quality management (QM) data to assess and manage the overall project quality,
with a focus on safety aspects.

130
131
The following notations are used in Table: Follow (F), Assist (A), Perform (P), Lead (L), Create (C).

Table
Software Safety Skill Sets and Activities by Competency Level
Levels

Skill Sets Freshers T1 T2 T3 T4

1. Using tools, con ducts
Requirements 1. Assists in collecting for mal system hazard 1. Verifies complete ness
data for the creation of a 1. Creates and verifies analyses verifying safety and correctness of safety
hazard list. (F/A) preliminary hazard lists. models. (P) requirements. (/L)
(A/P)

2. Assists in the iden 2. Uses software tools to

tification of top level build safety models (FTA,
mishaps and their causes. ETA, FMEA). (A/P)
(F/A)

132
 2. Interacts with system
and software engineers
3. Assists with the 3. Assists in safety to assure that safety
installation of safety and requirements iden 2. Identifies safety requirements are
reliability tools. (F/A) tification. (F/A) requirements. (P) complete and realizable.
(L)

3. Assures that safety 1. Creates or pro poses

Requirements requirements are new methods for safety
included in the overall assessment, mitigation,
system requirements. (P) and verification. (C)

1. Implements design 1. Verifies complete ness 1. Creates or pro poses

Design 1. Assists in identifying solu tions to assure that 1. Proposes and selects and correct ness of the new design solutions,
mitigation techniques for the hazards are design solutions to design, including safety leading to the increased
defined safety require mitigated and the safety assure the hazards are hazards and safety qual safety
ments. (F/A) require ments are met. mitigated. (P) ities. (P/L) of new
(A) designs. (C)

133
 2. Supervises the design 2. Leads the project in
team. Analyzes risk and deciding the proposed
2. Follows the recom verifies design from a architectural solutions to
mended design prin safety perspective. (P/L) mitigate hazards. (L)
ciples. (P)

2. Leads the project in

deciding the proposed
architectural solutions to 3. Evaluates risk related
mitigate hazards. (L) to design for safety. (P/L)

Table
Software Safety Skill Sets and Activities by Competency Level
Levels

Skill Sets Freshers T1 T2 T3 T4

134
 1. Implements large code
Development components and their
interfaces, considering 1. Implements the archi 1. Establishes 1. Creates new stan
safe coding practices to tecture and design to organization standards to dards to ensure code
avoid safety violations. ensure code safety. (P ensure code safety. (L/C) safety. (C)
(A/P) / L)
2. Manages the 2. Oversees and verifies
interfacing of large code that the safety aspects of
components with special the design are imple
attention mented in the pro duced
to poten tial safety code. (L)
issues. (P/L)
1. Contributes
Testing expertise to establish
1. Assists in the installa 1. Performs testing using 1. Selects appropriate 1. Establishes new organization
tion of tools and infra tools with a focus on testing techniques to organization standards guidelines related to
structure for safety safety requirements. assure the safety of the for safety valida testing the safety of
requirements testing. (A/P) application. (P) tion and verification. software intensive
(F/A) (L/C) applications. (C)

2. Applies 2. Manages the project,

Testing applicable being responsible for
industry overall safety and
standards meeting industry
to assure guidelines. (L)
that the
product
meets
industry
safety crite
ria. (P)

135
 1. Identifies artifacts 1. Contributes to and
Process 1. Assists in required to establish the verifies the complete
the collec safety case, following ness of the safety case, 1. Leads the safety team
tion of data industry standards. (A/P) following selected responsible for the proj
to establish industry criteria. (P) ect safety case. (L)
the project
safety case.
(F/A)

2. Establishes
organization 1. Contributes
standards expertise to establish
for safety better means of
assessment assessing safety. (C)
processes
and selec
tion of
safety crite
ria. (L/C)

1. Contributes
Quality 1. Supervises expertise to improve
1. Assists in the col 1. Collects safety QM collection of QM data 1. Manages the overall means of measuring and
lection of safety QM data and reports the and their compatibility project quality with a establishing the safety
data. (A) project status. (A/P) with the focus quality of the
safety case. (P/L) on safety aspects. (L) product and
process. (C)

136
Software Configuration management system: DevOps

Table
Software Configuration Software Configuration Management
Management Skill Sets Activities
Determine organizational context for and constraints on SCM.
Identify software components to be controlled by SCM.
Design data and code repositories.
Plan versioning procedures for path branching and path integration.
Plan SCM Develop/adopt a change control process.
Identify and procure SCM tools.
Establish SCM library.
Develop SCMP.

Follow SCMP.
Use SCM tools.
Control path branching and path integration during development.
Conduct SCM Generate, classify, and manage problem
reports.
Maintain and update SCM baselines.
Prepare SCM reports.
Conduct SCM audits.

137
 Develop software release plan.
Identify and procure software release tools.
Manage Software Releases Use software release tools.
Produce software releases.
Design and implement tools and procedures for generating patches to be delivered.

Software Measurement Skills:

Table
Software Measurement Skill Sets Software Measurement Activities

Identify measurement needs.

Define measures.
Select measures and measurement scales.
Establish data collection and analysis methods.
Plan Measurement Process Set target values and thresholds.
Establish report formats and reporting
procedures.
Identify measurement tools.
Procure and install measurement tools.
Plan for data storage.
Use measurement tools and manual
procedures to collect data.
Perform Measurement Validate collected data.
Process Retain valid data in a repository.
Generate and distribute reports.
Identify and recommend improvements to the
measurement process.

138
The following notations are used in Table : Follow (F), Assist (A), Perform (P), Lead (L), Create (C).

Table
Software Measurement Skill Sets and Activities by Competency Level
Levels

Skill Sets Freshers T1 T2 T3 T4

1. Defines attributes of
Plan 1. Participates in the process and
Measurement identifying measures product measures to
Process for an organization. (P) be used throughout an
organisation. (C)

139
1. Participates in 2. Leads identification
identifying mea of measurement needs 2. Develops new ways
surement needs for a for a project or to identify mea
project or program. (P) program. (L) surement needs. (C)
2. Assists in selecting 3. Selects measures 3. Defines new mea
measures and mea and mea surement sures and measure
surement scales. (A) scales. (L) ment scales. (C)
4. Reviews and
3. Establishes data col approves data col 4. Develops new data
lection and analysis lection and analysis collection and analysis
methods. (P) methods. (L) methods. (C)

140
 4. Participates in
Plan setting target values 5. Sets target values
Measurement and thresholds. (P) and thresh olds. (L)
Process
5. Participates in 6. Establishes report 5. Develops new report
establish ing report for mats and reporting formats and reporting
formats and reporting procedures. (L) procedures. (C)
procedures. (P)

7. Reviews and 6. Develops new mea

6. Identifies measure approves measure surement tools and
ment tools and manual ment tools and manual manual procedures. (C)
procedures. (P) procedures. (L)

8. Reviews and
1. Assists in planning 7. Plans for data stor approves plan for data
for data storage. (A) age. (P) storage. (L)

2. Assists in selecting 8. Selects data col 9. Approves data col

data col lection and lection and analysis lection and analysis
analysis methods. (A) methods. (P) methods. (L)

141
142
Table
Software Measurement Skill Sets and Activities by Competency Level
Levels

Skill Sets Freshers T1 T2 T3 T4

Plan 3. Assists in identifying 9. Selects measure 10. Approves measure
Measurement 1. Procures and installs measurement tools ment tools and manual ment tools and manual
Process measurement tools. (L) and manual procedures. (A) procedures. (A)
procedures. (A)
1. Periodically reviews
Perform methods, tools, and
Measurement 1. Uses measure ment 1. Uses manual pro 1. Leads and coor techniques used to
Process tools to collect data. (P) cedures to collect data. dinates the measure perform the measure
(P) ment process. (L) ment process. (C)
2. Modifies existing and
develops new review
2. Approves tactical methods, tools, and
2. Maintains valid data 2. Assists in validating improvements to the techniques used to
in a repository. (P) collected data. (A) 1. Validates collected measurement process. perform the measure
data. (P) (L) ment pro cess. (C)

143
 3. Identifies and rec
ommends improve
3. Generates and ments to the mea
distributes reports (P) surement process. (A)

Gap Analysis:

Gap Analysis Worksheet

144
Date Completed:
Engineering Dept:
Completed by: [names and titles of those completing the worksheet]
Competencies (from Tables A and B of the in4Velocity Skill Areas)
Skills Have Need Gap
Software Requirements Skills
Software Requirements Elicitation
Software Requirements Analysis
Software Requirements Specification
Software Requirements Verification and Validation
Software Requirements Process and Product Management

Software Design Skills

Software Design Fundamentals
Software Design Strategies and Methods
Software Architectural Design
Software Design Quality Analysis and Evaluation
Software Development Skills
Software Development Planning
Note: Analysis may be at the level of skill area or skill
Note: Have, Need, and Gap indicate the number of individuals and the
competency level

145
Gap Analysis Worksheet
Date Completed:
Engineering Dept:
Completed by: [names and titles of those completing the worksheet]
Competencies (from Tables A and B of the in4Velocity Skill Areas)
Skills Have Need Gap
Managing Software Development
Detailed Design and Coding
Debugging and Testing
Integrating and Collaborating
Software Testing Skills
Software Test Planning
Software Testing Infrastructure
Software Testing Techniques
Software Testing Measurement and Defect Tracking

Software Sustainment Skills

Software Transition
Software Support
Software Maintenance
Software Process and Life Cycle Skills

146
Software Development Life Cycle Implementation
Process Definition and Tailoring
Process Implementation and Management
Process Assessment and Improvement
Software Systems Engineering Skills
System Development Life Cycle modelling
Concept Definition
System Requirements Engineering
System Design
Requirements Allocation
Component Engineering
System Integration and Verification
Note: Analysis may be at the level of skill area or skill
Note: Have, Need, and Gap indicate the number of individuals and the
competency level

147
Gap Analysis Worksheet
Date Completed:
Engineering Dept:
Completed by: [names and titles of those completing the worksheet]
Competencies (from Tables A and B of the in4Velocity Skill Areas)
Skills Have Need Gap
System Validation and Deployment
System Sustainment Planning
Software Quality Skills
Software Quality Management (SQM)
Reviews

148
Audits
Statistical Control
Software Security Skills
Requirements
Design
Development
Testing
Process
Quality
Software Safety Skills
Requirements
Design
Development
Testing
Process
Quality
Software Configuration Management Skills
Plan SCM
Conduct SCM
Manage Software Releases
Software Measurement Skills
Plan Measurement Process
Note: Analysis may be at the level of skill area or skill
Note: Have, Need, and Gap indicate the number of individuals and the
competency level

Skills Have Need Gap

Perform Measurement Process

149
Note: Analysis may be at the level of skill area or skill
Note: Have, Need, and Gap indicate the number of individuals and the
competency level

Individual Gap Analysis Worksheet

Date Completed:

150
Gap Analysis for: [name of individual]
Names and Titles of Other Participants:
Competencies (from Tables A and B of the in4Velocity Skill Areas)
Skills Have Need Gap
Software Requirements Skills
Software Requirements Elicitation
Software Requirements Analysis
Software Requirements Specification
Software Requirements Verification and Validation
Software Requirement Process and Product Management
Software Design Skills
Software Design Fundamentals
Software Design Strategies and Methods
Software Architectural Design
Software Design Quality Analysis and Evaluation
Software Development Skills
Software Development Planning
Managing Software Development
Detailed Design and Coding
Debugging and Testing
Integrating and Collaborating
Software Testing Skills
Software Test Planning
Software Testing Infrastructure
Software Testing Techniques
Software Testing Measurement and Defect Tracking
Software Sustainment Skills
Software Transition

151
Note: Have indicates that competencies for all activities for a skill at the indicated level have been demonstrated (e.g., L2); Gap indicates the
difference
Note: Need includes the activity numbers for which competency must be demonstrated to advance to the next level for that skill

152
Individual Gap Analysis Worksheet
Date Completed:
Gap Analysis for: [name of individual]
Names and Titles of Other Participants:
Competencies (from Tables A and B of the in4Velcity Skill Areas)
Skills Have Need Gap
Software Support
Software Maintenance
Software Process and Life Cycle Skills
Software Development Life Cycle Implementation
Process Definition and Tailoring
Process Implementation and Management
Process Assessment and Improvement
Software Systems Engineering Skills
System Development Life Cycle Modeling
Concept Definition
System Requirements Engineering
System Design
Requirements Allocation
Component Engineering
System Integration and Verification
System Validation and Deployment
System Sustainment Planning

153
Software Quality Skills
Software Quality Management (SQM)
Reviews
Audits
Statistical Control
Software Security Skills
Requirements
Design
Note: Have indicates that competencies for all activities for a skill at the indicated level have been demonstrated (e.g., L2); Gap indicates the
difference
Note: Need includes the activity numbers for which competency must be demonstrated to advance to the next level for that skill

154
Individual Gap Analysis Worksheet
Date Completed:
Gap Analysis for: [name of individual]
Names and Titles of Other Participants:
Competencies (from Tables A and B of the in4Velocity Skill Areas)
Skills Have Need Gap
Development
Testing
Process
Quality
Software Safety Skills
Requirements
Design
Development
Testing

155
Process
Quality
Software Configuration Management Skills
Plan SCM
Conduct SCM
Manage Software Releases
Software Measurement Skills
Plan Measurement Process
Perform Measurement Process
Note: Have indicates that competencies for all activities for a skill at the indicated level have been demonstrated (e.g., L2); Gap indicates the
difference
Note: Need includes the activity numbers for which competency must be demonstrated to advance to the next level for that skill

156