IT Methodology Webinar - PDF Free Download

IT Methodology Webinar Explore the Software Testing Lifecycle Initiate Project Intelligence

Things to Know All participants will be on mute Questions are welcome Ask questions in the question box We DO NOT send out PDU certificates May be valid for PDU credit (self-report session) - For more information check out article on Webinars and PDUs http://www.projectinsight.net/support/kb/webinars-and-pdus

Moderator Denise Rodriguez Project Insight Marketing Denise.Rodriguez@projectinsight.com www.projectinsight.net

Project Insight Schedule a customized demo today! +1 (949) 476-6499 x3 info@projectinsight.net Request info: www.projectinsight.net

Presenter Cameron Watson President, QAIassist cwatson@qaiassist.com www.qaiassist.com

Who s on the call? 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 is QAIassist? 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

IT Methodology Webinar Audience 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

QAIassist 2016 Series - Goals 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)

2016 Schedule 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 (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.

2016 Concept Sessions The 3rd Wednesday of Month (Jan, Mar, May, Jul, Sept, Nov) 8:00 am Pacific - 11:00 am Eastern Time IT Methodology Concepts (60 mins) 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)

2016 Tutorial Sessions The 3rd Wednesday of Month (Feb, Apr, Jun, Aug, Oct) 8:00 am Pacific - 11:00 am Eastern Time 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)

Explore the Software Testing Lifecycle 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)

Explore the Software Testing Lifecycle Concept IV - Agenda 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

Concepts I A Context for IT Methodology 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

IT Methodology Context 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 Map & Journey 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/Lifecycle - Noun All Methodologies/Lifecycles (RUP, QAIassist-IM, PMI, Prince2) define, utilize and rely on their own pre-defined structure, naming conventions, and terminology Hierarchy/Structure Methodology/Lifecycle (ie Project Management, Software Development, Software Testing) Phase/Stage (ie Initiate, Planning, Design, Closeout) Deliverable/Artifact/Work Product (ie Project Charter, Testing Strategy) Activity (tasks performed to complete deliverables, artifacts, work products)

QAIassist Integrated Methodology

Deliverable/Artifact/Work Product versus Activity Building an IT Application Deliverable (Artifact, Work Product) Business Case Project Plan User Acceptance Test Plan Activity (non-deliverable, non-artifact, non Work Product) Reviewing business need with Operational Management, Business Analysts and End-Users Meeting with Stakeholders to acquire approval of Project Plan Discussing User Acceptance Testing objectives and priorities with testing team

Deliverable/Artifact/Work Product Attributes 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 Status 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

QAIassist Integrated Methodology

SDLC Business Context 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

SDLC IT Context Multiple IT Environments Mainframe, Distributed, Web Based Multiple Delivery Approaches Methodology (verb) Waterfall Agile Prototyping Integrations Project Management Lifecycle Software Testing Lifecycle

SDLC Inherent Principle How many requirements (and associated functionality) should/can be developed? Too Few leads to a solution that does not satisfy the business need Too Many leads to a solution that is over priced, over built, over budget and past due (and may still not satisfy the business need) How can a project team know when they are best leveraging an SDLC to develop the appropriate level of functionality?

SDLC Premise

SDLC Requirements (Identification and Definition) Sample Application Accounting Receivables Payables Payroll Customer Attained Services Calculated Invoice Sent Payment Received Invoice Received Invoice Paid Hours Worked Vacation Days Wages Paid

SDLC Requirements (Identification & Definition) Data Context Subject Accounting Topics Receivables Payables Payroll Entities Customer Attained Invoice Received Hours Worked Services Calculated Invoice Paid Vacation Days Invoice Sent Wages Paid Payment Received

SDLC Requirements (Identification & Definition) Process Context Accounting System Receivables Payables Payroll Sub-Systems Customer Attained Services Calculated Invoice Sent Invoice Received Invoice Paid Hours Worked Vacation Days Functions Payment Received Wages Paid

SDLC Requirements (Identification & Definition) Process Naming Convention Accounting S1 System Receivables SS1 Payables SS2 Payroll SS3 Sub-Systems Customer Attained Services Calculated Invoice Sent SS1-F1 SS1-F2 SS1-F3 Invoice Received Invoice Paid SS2-F1 SS2-F2 Hours Worked Vacation Days SS3-F1 SS3-F2 Functions Payment Received SS1-F4 Wages Paid SS3-F3 Client Marketing Sales Promotion CRM SS1-F1-P1 SS1-F1-P2 SS1-F1-P3 Modules/Programs

QAIassist Integrated Methodology

SDLC - Mechanics High Level Solution Design Deliverable (S1, SSX, SSX-FX) Accounting S1 System Receivables SS1 Payables SS2 Payroll SS3 Sub-Systems Customer Attained SS1-F1 Invoice Received SS2-F1 Hours Worked SS3-F1 Functions Services Calculated SS1-F2 Invoice Paid SS2-F2 Vacation Days SS3-F2 Invoice Sent SS1-F3 Wages Paid SS3-F2 Payment Received SS1-F4

QAIassist Integrated Methodology

SDLC - Mechanics Detail Solution Design Deliverables (SSX-FX one per) Accounting S1 System Receivables SS1 Payables SS2 Payroll SS3 Sub-Systems Customer Attained SS1-F1 Invoice Received SS2-F1 Hours Worked SS3-F1 Functions Services Calculated SS1-F2 Invoice Paid SS2-F2 Vacation Days SS3-F2 Invoice Sent SS1-F3 Wages Paid SS3-F2 Payment Received SS1-F4

SDLC - Mechanics Programming Specifications (SSX-FX-PX one per) Accounting System Receivables SS1 Sub-Systems Customer Attained Services Calculated Invoice Sent Payment Received SS1-F1 Functions Client Marketing Sales Promotion CRM SS1-F1-P1 SS1-F1-P2 SS1-F1-P3 Modules/Programs

QAIassist Integrated Methodology

Software Development Requirements Deliverables & Dependencies High Level Solution Design deliverable Identifies data Subject and process Systems Identifies data Topics and process Subsystems Identifies data Entities and process Functions Detailed Solution Design deliverable(s) One deliverable for every Function as identified in the High Level Solution Design deliverable Functionality defined (Manual and Automated) All required Unit Modules/Programs are identified Programming Specification deliverable(s) One deliverable for every Unit Module/Program as identified in the Detailed Solution Design deliverables Specifics for each Unit Module/Program are described

Software Development Lifecycle (SDLC) Objectives Establish a foundation for ongoing collaboration and communication between Business/User Community and Information Technology/IT resources Business/User community contributes to and authorizes formal requirements and deliverables throughout the completion of the project necessary documentation Computer Unit Code is developed/built to reflect the authorized and required functionality (design and business requirements) Computer Unit Code is successfully unit tested against the authorized design and business requirements - satisfactory code is made available for additional testing End User training is planned and delivered

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

STLC Fundamentals 101 Viable STLC methodologies (noun and verb) are designed to help not hinder STLC methodologies (noun) are applicable for a wide range of STLC 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 STLC methodology (noun) can best be applied or leveraged by an organization or project team No silver bullet exists - if the perfect combination of an STLC Methodology (noun) and STLC Methodology (verb) existed, every project team and organization would be using it

STLC Fundamentals 102 STLC deliverables (and content) may be re-usable from one project to another Not every STLC 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 STLC deliverable has to be completed for every project - information used to populate every deliverable must add value (cost, schedule, quality) to the project

STLC Business Context 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 IT Context Multiple IT Environments Mainframe, Distributed, Web Based Multiple Delivery Approaches Methodology (verb) Waterfall Agile Prototyping Integrations Project Management Lifecycle Software Testing Lifecycle

Software Testing Lifecycle (STLC) Phases STLC objectives are achieved utilizing five phases, they are : Systems Analysis Design Build Test (Unit) Release

IT Methodology

IT Methodology STLC Systems Analysis Phase

STLC Systems Analysis Phase 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 Deliverables 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.

STLC - 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.

STLC - Systems Analysis Phase Deliverables 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.

IT Methodology STLC Design Phase

STLC Design Phase Objectives review all authorized project documentation define system integration testing plans and evaluation criteria Iterations iterative within the phase (waterfall) iterative within the lifecycle (agile)

STLC - Design Phase Deliverables System Integration Test Plan(s) - (exit) Used to define how all of the testing activities are to be executed prior to the 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.

STLC - 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.

IT Methodology STLC Build Phase

STLC Build Phase 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 iterative within the phase (waterfall) iterative within the lifecycle (agile)

STLC - Build Phase Deliverables 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.

STLC - 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.

IT Methodology STLC Test Phase

STLC Test Phase Objectives 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 iterative within the phase (waterfall) iterative within the lifecycle (agile)

STLC - Test Phase Deliverables System Integration Test Plan(s) Used to define how all of the testing activities are to be executed prior to the 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.

STLC - 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.

STLC - Test Phase Deliverables 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.

STLC - Test Phase Deliverables 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.

IT Methodology STLC Release Phase

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 iterative within the phase (waterfall) iterative within the lifecycle (agile)

STLC - Release Phase Deliverables User Acceptance Test Plan 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.

STLC - 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.

STLC - Release Phase Deliverables 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.

STLC - Release Phase Deliverables 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.

Internal Dynamics - STLC Interfaces 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

STLC with Software Development Lifecycle (SDLC) Unit Test Planning, Execution & Authorization

STLC with Software Development Lifecycle (SDLC) System Integration Test Planning, Execution & Authorization

STLC with Software Development Lifecycle (SDLC) User Acceptance Test Planning, Execution & Authorization

IT Methodology

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) (wwwqaiassist.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

2016 Concepts Schedule The 3rd Wednesday of Month (Jan, Mar, May, Jul, Sept, Nov) 8:00 am Pacific - 11:00 am Eastern Time IT Methodology Concepts (60 mins) Methodology for the IT Landscape - (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)

2016 Tutorials Schedule The 3rd Wednesday of Month (Feb, Apr, Jun, Aug, Oct) 8:00 am Pacific - 11:00 am Eastern Time 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)

Moderator Denise Rodriguez Project Insight Marketing Denise.Rodriguez@projectinsight.com www.projectinsight.net

Join us! Twitter LinkedIn Facebook Instagram YouTube

Learn more Schedule a customized demo today +1 (949) 476-6499 x3 info@projectinsight.net Request info: www.projectinsight.net Contact QAIassist +1 (613) 523-0052 solutions@qaiassist.com Request info: www.qaiassist.com

PI Community Sign up for more! IT Methodology & Agile PM training Leadership Product training Check out the videos