it methodology webinar - project insightdownloads.projectinsight.net/training/it... · explore the...

IT Methodology WebinarIT Methodology Webinar

Explore the Software Testing Lifecycle

Things to Know…

All participants will be on mute

Questions are welcome

Ask questions in the question box

May be valid for PMI Category C PDUs

We do not mail out PDU certificates

Moderator

Denise Rodriguez

Project Insight

Marketing

[email protected]

www.projectinsight.net

Presenter

Cameron Watson

President, QAIassist

[email protected]

www.qaiassist.com

I am a Project Manager

I am a Business or Operational Manager

I am a software developer or software tester

I am a member of an organizational PMO, governance or quality

assurance function

I want a better understanding of IT Methodology

Who’s on the call?

Established 2007 – Ottawa, Canada

Nurturing organizational efficiency through IT Methodology knowledge & expertise

Support and promote a community with evolving IT Methodology knowledge and expertise

Maintain, optimize, promote and support the delivery of IT methodology products and

lifecycles proven to increase operational performance

Administration and oversight of QAIassist Integrated Methodology (QAIassist-IM) and formal

certifications – “Foundation” & “Practitioner”

Support practitioners and authorized affiliates in acquiring and delivering IT Methodology

knowledge and expertise

Who is QAIassist?

Nurturing efficiency through IT Methodology knowledge & expertise across the globe

� Over 200 countries

� Wide array of industries (manufacturing, banking, health, insurance, consulting)

� More than 50 unique webinars

Over 10,000 webinar registrants

� Executives

� Operational & Delivery Managers

� Project Managers

� Business Analysts and Architects

� Application Developers & Testers

� Corporate PMO, Quality Assurance, Continuous Improvement

� Consultants

IT Methodology Webinar Audience

Share IT Methodology knowledge

Develop IT methodology understanding &

expertise

Provide additional insight into several IT (project

management, software development, software

testing) methodologies

Discuss best practices on incorporating an

organizational IT methodology

Promote ongoing dialog and feedback with

webinar audience (questions, email, survey)

QAIassist 2015 Series - Goals

IT Methodology experience and knowledge level of webinar audiences is varied

� “Fledgling” seeking to acquire general and conceptual IT Methodology information

� “Veterans” and seeking “nuts and bolts” and more detailed IT Methodology information

� Most attendees are seeking more interaction and dialog (questions, polls, surveys, feedback)

throughout the webinar sessions

2014 Survey Results

The 3rd Wednesday of Every Month

� 8:00 am Pacific - 11:00 am Eastern Time

IT Methodology Concepts (60 mins)

� This series of six webinars will be presented on a bi-monthly basis. Each webinar

will provide you with a context, overview, terminology and general understanding

of information technology (IT) methodology.

IT Methodology – Tutorials (45 mins)

� This series of five webinars will be presented on a bi-monthly basis. Each session is

designed to offer a more “hands on” perspective – bridging the concepts into a

practical utilization.

2015 Schedule

2015 “Concepts” Schedule

The 3rd Wednesday of Month (Jan, Mar, May, Jul, Sept, Nov)



� A Context for IT Methodology - (Jan)

� Apply PM Fundamentals to IT - (Mar)

� Leverage the Software Development Lifecycle - (May)

� Explore the Software Testing Lifecycle - (Jul)

� Incorporate Organizational Process Governance - ( Sept)

� Implementing IT Methodology - (Nov)

2015 “Tutorials” Schedule

The 3rd Wednesday of Month (Feb, Apr, Jun, Aug, Oct)


IT Methodology Tutorials (45 mins)

� Applying IT Methodology to Project Initiation - (Feb)

� Project Planning & Design with IT in Mind - (Apr)

� Executing Projects with IT Methodologies - (Jun)

� Project Control & Verification - (Aug)

� Project Close & Delivery - ( Oct)





� A Context for IT Methodology - (Jan)







Concept IV - Goals

� Familiarize previous “Concept” sessions (Jan, Mar, May)

� Identify a context for Software Testing Lifecycle (STLC)

� Define the purpose and objectives of STLC phases

� Review (at high level) STLC deliverables

� Understand STLC interfaces (PMLC & SDLC)

Establish webinar context - review previous “Concept” sessions

� Jan - A Context for IT Methodology

� Mar- Apply PM Fundamentals to IT

� May - Leverage the Software Development Lifecycle

Software Testing Lifecycle (STLC) – Objectives, Fundamentals, Context

STLC Phases - Objectives, Iterations, Deliverables

STLC – Internal Dynamics (PMLC and SDLC interfaces)

Recap


Concept IV - Agenda

IT Methodology - general context

IT Methodology - as a “noun” and a “verb”

IT Methodology constructs and hierarchy - “noun” (lifecycles, phases, deliverables)

IT Methodology - “verb” (waterfall, agile, spiral, RAD)

IT Methodology structure & deliverable examples - “noun” (project management, software

development, software testing)

IT Methodology - organizational compatibility and benefits

Recap

Concepts I

A Context for IT Methodology

Agenda

Organizational Frameworks

� ISO(900XXX), CMMI, Six-Sigma, ITIL, COBIT

Methodologies/Lifecycles (noun)

� Rational Unified Process (RUP), QAIassist

(IM), PMI, Prince2

Methodologies/Lifecycles (verb)

� Waterfall, Spiral, Agile, RAD, etc

IT Methodology Context

Methodologies/Lifecycles - “noun”

� The roadmap

� Rational Unified Process (RUP),

QAIassist (IM) , PMI, Prince2

Methodologies/Lifecycles - “verb”

� The journey taken along the road

� Waterfall, Spiral, Agile, RAD ,

Prototyping, etc

IT Methodology – Map & Journey

“Waterfall” Methodology/Lifecycle

� a single iteration through the methodology/lifecycle (noun)

� deliverables/artifacts defined, assigned, and documented

� formal structure required

“Agile” Methodology/Lifecycle

� more than a single iteration through a methodology/lifecycle (noun)

� limited deliverable creation

� formal structure not required

Methodology/Lifecycle – Verb

Context – Building an Accounting Application

� Accounts Payable

� Accounts Receivable

� Payroll


QAIassist Integrated Methodology








Recap


Concept IV - Agenda

Review IT Methodology context (terminology, structure, fundamentals)

Discuss the concept and significance of the term “deliverable”

Establish a Project Management context

Define Project Management phases (purposes, objectives, iterations)

Review Project Management benefits (Project & Process)

Recap

Concepts II – Apply PM Fundamentals to IT

Agenda

Building a House

Deliverable (Artifact, Work Product)

� Blue Prints

� Foundation completed

� Windows installed

Activity (non-Deliverable, non-Artifact, non Work Product)

� Meeting with Architect to review Blue Prints

� Mixing concrete to pour the foundation

� Authorizing purchase of the wood needed to complete the window frame

“Deliverable/Artifact/Work Product” versus “Activity”

Building an IT Application

Deliverable (Artifact, Work Product)

� Project Plan

� Business Case

� User Acceptance Test Plan

Activity (non-Deliverable, non-Artifact, non Work Product)

� Meeting with Stakeholders to acquire approval of Project Plan

� Reviewing business need with Operational Management, Business Analysts and End-Users

� Discussing User Acceptance Testing objectives and priorities with testing team

“Deliverable/Artifact/Work Product” versus “Activity”

Fixed Sections (always populated)

� Title Page

� Deliverable Details (Author, Creation Date, Version, Status, etc)

� Deliverable History, Reviewers, Sign Off

� Table of Contents (as per deliverable)

� Context (purpose of the deliverable)

Variable Sections (based on pre-defined informational requirements)

� Structure/format defined as per deliverable (ie a Project Charter deliverable does not

have the same pre-defined informational requirements as a Testing Strategy deliverable)

Deliverable/Artifact/Work Product

Construct/Format

Draft - Deliverable has been identified, assigned and is in the process of being

drafted/completed

Review - “Draft” deliverable has been completed and submitted for “review” and

“authorization”

Approved/Archived - “Reviewed” deliverable has been “Authorized” by designated

stakeholders and put under configuration management

Applied - Information within “Authorized” deliverable is being referenced and/or utilized

within another deliverable

Deliverable/Artifact/Work Product Status

Tangible (pre-defined informational requirements)

� Can be identified and defined (completion dates, cost) on Project Schedule

� Can be assigned (populating information requirements) to project team member(s)

� Can be referenced by project team members to support creation of other deliverables

� Can be formally reviewed and officially authorized

� Will alter in status (authored, reviewed, approved, archived, referenced) throughout life of project

� Will reflect evolving deliverable and project status/progress (risks, issues, percentage complete)

� Can be placed under formal configuration management – re: with evolving status

� Can be accessed for future reference (application support and maintenance)

“Deliverable/Artifact/Work Product” Attributes

Integration






STLC Phases - Objectives, Iterations, Traceability


Recap

Leverage the Software Testing Lifecycle

Concept IV - Agenda








Recap


Concept IV - Agenda

Software Testing Lifecycle (STLC) Objectives

A viable Software Testing Lifecycle (STLC) should consistently ensure the

delivery of reliable and authorized solutions

� Prerequisite – an official project must exist – defined and approved

� Plan, deliver and execute all necessary testing deliverables and activities

� Synchronization of STLC deliverables and activities with PMLC and SDLC

� Ensure the solution adheres to the business need and all approved user requirements

� Ensure solution achieves user expectations and authorization prior to delivery

Viable IT methodologies (noun and verb) are designed to help not hinder

IT methodologies (noun) are applicable for a wide range of IT Methodologies (verb) and

delivery approaches (waterfall, spiral, agile, RAD, prototyping, etc)

No hard or specific rules (ie iterations, frequency of iterations, deliverables to be

completed) of how an IT methodology (noun) can best be applied or leveraged by an

organization or project team

No silver bullet - if the perfect combination of IT Methodology (noun) and IT

Methodology (verb) existed, every project team and organization would be using it

STLC Fundamentals 101

Deliverables (and content) may be re-usable from one project to another

Not every deliverable of every phase has to be completed for every project

- any and every deliverable to be completed must add value (cost,

schedule, quality) to the project

Not every section or sub-section of every deliverable has to be completed

for every project - information used to populate every deliverable must add

value (cost, schedule, quality) to the project

STLC Fundamentals 102

Development Environment

� New Products

� New Operational Business Applications (ie HR, Accounting, Sales, etc)

Maintenance/Support Environment

� Existing Products

� Existing Operational Business Applications (HR, Accounting, Sales, etc)

� Off the Shelf Applications

STLC – Business Context

Multiple IT Environments

� Mainframe, Distributed, Web Based

Multiple Delivery Approaches – Methodology (verb)

� Waterfall

� Agile

� Prototyping

Integrations

� Project Management Lifecycle

� Software Testing Lifecycle

STLC – IT Context








Recap


Concept IV - Agenda





Software Testing Lifecycle (STLC) – Purpose, Fundamentals, Context


STLC – Internal Dynamics (PMLC and STLC interfaces)

Recap


Concept IV - Agenda

STLC objectives (previous page) are achieved utilizing five

phases, they are :

� Systems Analysis

� Design

� Build

� Test (Unit)

� Release

Software Testing Lifecycle (STLC) Phases

STLC objectives (see previous page) are achieved utilizing five

phases, they are :

� Systems Analysis

� Design

� Build

� Test (Unit)

� Release

Software Testing Lifecycle (STLC) Phases

Objectives

� ensure a formal project exists and has been authorized

� review all authorized pre-project documentation

� establish a strategy for testing the application functionality

� define user acceptance testing plans and evaluation criteria

Iterations

� iterative within the phase (waterfall)

� iterative within the lifecycle (agile)

STLC – Systems Analysis Phase

Testing Strategy (exit)

Used to define a conceptual view of how all of the testing activities are to be executed

throughout the life of the project. It identifies the high level testing tasks to be completed in

each of the testing environments (unit, integration, user acceptance) the testing standards to

be applied across all testing environments, the testing tools to be used, the testing deliverables

to be completed, and the standards used to identify the acceptance criteria used for testing.

Systems Analysis Phase - Deliverables

User Acceptance Test Plan (exit)

Used to define how all of the testing activities are to be executed prior to the

application/product being migrated into the production environment. It identifies the testing

tasks to be completed within the UAT environment, the testing standards to be applied within

the UAT environment, the testing tools to be used, the testing deliverables to be completed,

and the standards used to define the UAT evaluation criteria.


User Acceptance Testing Evaluation Criteria (exit)

Used to document the "expected" User Acceptance Test evaluation criteria prior to conducting

user acceptance testing. This criteria is used to evaluate “expected” results versus “actual”

results. Functionality that "passes" the user acceptance testing is ready to be migrated to the

production environment. Functionality that "fails“ the user acceptance testing is recorded and

requires further attention and activity from the project team.


Objectives

� review all authorized project documentation

� define system integration testing plans and evaluation criteria

Iterations



STLC – Design Phase

System Integration Test Plan(s) - (exit)


application/product being migrated into the User Acceptance Test (UAT) environment. It

identifies the testing tasks to be completed within the SIT environment, the testing standards

to be applied within the SIT environment, the testing tools to be used, the testing deliverables

to be completed, and the standards used to define the SIT evaluation criteria.

Design Phase - Deliverables

System Integration Test Evaluation Criteria (exit)

Used to document the "expected" System Integration Test evaluation criteria prior to

conducting System Integration Testing. This criteria is used to evaluate “expected” results

versus “actual” results. Functionality that "passes" the system integration testing is ready to be

migrated to the user acceptance environment. Functionality that "fails“ the system integration

testing is recorded and requires further attention and activity from the project team.

Design Phase - Deliverables

Objectives

� review all authorized project documentation

� complete all of the unit testing plan(s) and document the acceptance criteria for all of the

associated unit tests

� make unit test plans and evaluation criteria available - (to be executed against the technical

code generated during the build phase of the SDLC)

Iterations



STLC – Build Phase

Unit Test Plan(s)

Used to define how all of the unit testing activities are to be executed on the code/modules

being built/developed within the SDLC. It identifies the testing tasks to be completed within

the UT environment, the testing standards to be applied within the UT environment, the

testing tools to be used, the testing deliverables to be completed, and the standards used to

define the UT evaluation criteria.

Build Phase - Deliverables

Unit Test Evaluation Criteria (exit)

Used to document the "expected" Unit Test evaluation criteria prior to conducting Unit Testing

(referenced by SDLC). This criteria is used to evaluate “expected” results versus “actual” results.

Functionality that "passes" the Unit Testing is ready to be migrated to the System Integration

Testing environment. Functionality that "fails“ the user Unit Testing is recorded and requires

further attention and activity from the project team.

Build Phase - Deliverables

STLC – Test PhaseObjectives

� executing the System Integration Tests (SIT) as planned and against the pre-defined SIT

evaluation criteria (see STLC Design phase)

� document all testing deviations (difference between actual results and expected results using

System Integration Test evaluation criteria) in the SIT Defect Log – communicate deviations to

project team (for rework) – maintain Traceability Matrix

� release all viable (passing criteria) code functionality to the user acceptance environment for

additional testing

Iterations



System Integration Test Plan(s)


application/product being migrated into the User Acceptance Test (UAT) environment. It

identifies the testing tasks to be completed within the SIT environment, the testing standards

to be applied within the SIT environment, the testing tools to be used, the testing deliverables

to be completed, and the standards used to define the SIT evaluation criteria.

Test Phase - Deliverables

System Integration Test Evaluation Criteria

Used to document the "expected" SIT test evaluation criteria prior to conducting System

Integration testing. The System Integration test criteria is used to evaluate “expected” results

versus “actual” results. Functionality that "passes" the SIT tests is ready to be migrated to the

User Acceptance Test (UAT) environment. Functionality that "fails" these SIT tests is recorded

and requires further activity from the project team.


System Integration Test Defect Log

This deliverable is used to document and administer all of the "failed“ system integration tests

against the System Integration Test Evaluation Criteria deliverables. Each “failed" test is

assessed, documented and communicated to the project team who are required to make the

necessary changes to rectify the "failed“ test.


Requirements Traceability Matrix

Used to ensure all user defined requirements are documented and incorporated into the

application/system. It acts as the repository for all user requirements - it can be referenced and

cross checked to ensure all user requirements have been incorporated into the application

before it is released into the production environment.


STLC – Release Phase

Objectives

� executing the User Acceptance Tests (UAT) as planned and against the pre-defined UAT

evaluation criteria (see STLC Systems Analysis phase)

� document all testing deviations (difference between actual results and expected results using

User Acceptance Test evaluation criteria) in the UAT Defect Log – communicate deviations to

project team (for rework) – maintain Traceability Matrix

� release all viable (passing criteria) code functionality to the production environment once all

testing has been completed and authorized

Iterations



User Acceptance Test Plan


application/product being migrated into the production environment. It identifies the testing

tasks to be completed within the UAT environment, the testing standards to be applied within

the UAT environment, the testing tools to be used, the testing deliverables to be completed,

and the standards used to define the UAT evaluation criteria.

Release Phase - Deliverables

User Acceptance Test Evaluation Criteria

Used to document the "expected" User Acceptance Test evaluation criteria prior to conducting

user acceptance testing. This criteria is used to evaluate “expected” results versus “actual”

results. Functionality that "passes" the user acceptance testing is ready to be migrated to the

production environment. Functionality that "fails“ the user acceptance testing is recorded and

requires further attention and activity from the project team.


User Acceptance Defect Log

This deliverable is used to document and administer all of the "failed“ system integration tests

against the User Acceptance Test Evaluation Criteria deliverables. Each “failed" test is assessed,

documented and communicated to the project team who are required to make the necessary

changes to rectify the "failed“ test.


Requirements Traceability Matrix (exit)

Used to ensure all user defined requirements are documented and incorporated into the

application/system. It acts as the repository for all user requirements - it can be referenced and

crosschecked to ensure all user requirements have been incorporated into the application

before it is released into the production environment.






Software Testing Lifecycle (STLC) – Purpose, Fundamentals, Context



Recap


Concept IV - Agenda

Software Development Lifecycle

� Unit Test Plan(s)

� Unit Test Evaluation Criteria

Project Management Lifecycle

� Unit Test Authorization

� System Integration Test Authorization

� User Acceptance Test Authorization

Internal Dynamics - STLC Interfaces




Software Development Lifecycle (SDLC) – Fundamentals, Context



Recap


Concept III - Agenda

Body of Knowledge

Methodology/Lifecycle/Deliverables – www.qaiassist.com

� Project Management, Software Development, Software Testing

Body of Knowledge (Library) – www.qaiassist.com

� Methodology Origin – origins of methodology – identifies the differences

between the path we take (noun) and how we proceed (verb) down that path

� Context & Overview – provides a general overview of IT Methodology and how

it can be applied within an organization

� Deliverable Descriptions - provides general descriptions for all the deliverables

of the QAIassist Integrated Methodology

Until Next Session…

Keep Posing your Questions – call or send your questions in (Denise and/or

Cameron)

Explore the QAIassist Body of Knowledge – refer to the QAIassist Body of

Knowledge (sample deliverables, whitepapers, blog articles) – (www-

qaiassist.com)

QAIassist Practitioner - find out more about becoming QAIassist certified

“Foundation”, “Practitioner”

Tell your friends - tell your friends, coworkers and colleagues about the

Project Insight/QAIassist webinars – invite them to join us at the next session

Continuing Follow Up – send out a survey at the completion of every webinar,

follow up with attendees to obtain their suggestions and recommendation

2015 Schedule

The 3rd Wednesday of Every Month



� This series of six webinars will be presented on a bi-monthly basis. Each webinar

will provide you with a context, overview, terminology and general understanding

of information technology (IT) methodology.

IT Methodology – Tutorials (60 mins)

� This series of five webinars will be presented on a bi-monthly basis. Each session is

designed to offer a more “hands on” perspective – bridging the concepts into a

practical utilization.





� Methodology for the IT Landscape - (Jan)






2015 “Tutorials” Schedule

The 3rd Wednesday of Month (Feb, Apr, Jun, Aug, Oct)


IT Methodology Tutorials (60 mins)

� Applying IT Methodology to Project Initiation - (Feb)

� Project Planning & Design with IT in Mind - (Apr)

� Executing Projects with IT Methodologies - (Jun)

� Project Control & Verification - (Aug)

� Project Close & Delivery - ( Oct)

Learn more…

Denise Rodriguez

Project Insight

Marketing

[email protected]

www.projectinsight.net

Join us!

Follow us

Twitter @projectinsight

LinkedIn

Instagram @projectinsight

Like us

Facebook

Learn more…

Schedule a customized demo today

� +1 (949) 476-6499 x3

� [email protected]

� Request info: www.projectinsight.net

Contact QAIassist

� +1 (613) 523-0052

� [email protected]

� Request info: www.qaiassist.com

Project Insight Community

Sign up for more!

IT Methodology

PM training

Product training

Check out videos

it methodology webinar - project insightdownloads.projectinsight.net/training/it... · explore the...

Documents