IT Methodology Webinar - Project Insightdownloads.projectinsight.net › training › it-methodology...2014 Schedule The 3rd Wednesday of Every Month 8:00 am Pacific -11:00 am Eastern

IT Methodology Webinar

Leverage the Software Development Lifecycle

Things to know…

All participants will be on mute

Questions are welcome

� Please use the questions box to ask

questions

� The moderator will select questions

� All questions will be answered

today or by email at [email protected]

Webinar recording available in the PI Community

Denise Rodriguez

Project Insight

Marketing

[email protected]

www.projectinsight.net

Twitter: @projectinsight

Moderator

Cameron Watson

President, QAIassist

[email protected]

www.qaiassist.com

Presenter

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

Pioneer of IT Methodologies for small and mid-sized business (SMB’s)

Maintain and promote an IT Methodology body of knowledge (BOK) SMB’s

and practitioners rely on to optimize the delivery of products, services and

operational performance

Administer IT Methodology certification - “QAIassist Foundation”

Support practitioners and authorized affiliates in delivering IT Methodology

knowledge and expertise

Who is QAIassist?

IT Methodology Webinars delivered across the globe – 000’s attendees

Wide array of industries (health, manufacturing, consulting, finance)

Attendees

� Executive Management

� Business & Operational Management

� Project Managers

� Business Analysts

� Architects (Functional/Technical)

� PMO/Governance

� Programmers

� Testers/Quality Assurance

� Independent Consultant

IT Methodology Webinar Summary

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

QAIassist Webinar Series - Goals

2014 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 (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.

2014 “Concepts” Schedule

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



� 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)

2014 “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)


Webinar Goals

� establish a context for IT Methodologies (noun and verb)

� review fundamentals for applying IT Methodologies

� identify a context for Software Development Lifecycle (SDLC)

� define the purpose and objectives of SDLC phases

� review (at high level) SDLC deliverables

� assess SDLC scope (“project” versus “process”)

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)

Software Development Lifecycle (SDLC) – Fundamentals, Context, Depictions

SDLC Phases (objectives and iterations) & Deliverables

SDLC - “Project” versus “Process”

Recap


Agenda








Recap


Agenda

� ISO(900XXX)

� Agile

� CMMI

� ITIL

� Waterfall

� Rational Unified Process (RUP)

� QAIassist (IM)

� PMI

� Six-Sigma

� Prince2

� COBIT

Methodology – Terms, Terms

and more “terms”

IT Framework, IT Methodology, IT Lifecycle

� Non Standard usage in terminology

� Terms are used interchangeably between organizations and across the IT industry

� Examples include

• Project Management Methodology/Lifecycle/Framework

• Software Development Methodology/Lifecycle (SDLC)/Framework

• Software Testing Methodology/Lifecycle/Framework

� Every IT organization is using an IT Methodology or IT Lifecycle or IT Framework

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








Recap


Agenda








Recap


Agenda

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

Map = Noun, Journey = Verb








Recap


Agenda








Recap


Agenda

IT Methodology/Lifecycle - Noun

All Methodologies/Lifecycles (RUP, QAIassist, 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)

“Deliverable/Artifact/Work Product”

versus “Activity”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

IBM’s Rational Unified Process (RUP)

PMI’s Project Management Methodology

QAIassist Integrated Methodology








Recap


Agenda








Recap


Agenda

Map = Noun, Journey = Verb

Methodology/Lifecycle – Verb

Methodology/Lifecycle as a “verb” – journey

Project development and maintenance teams apply various

methodologies/delivery approaches, techniques and practices (waterfall,

spiral, agile, RAD, prototyping) to deliver applications - how they use the

roadmap (noun)

� Methodology/Delivery Approach, Techniques and Practices differ between

organizations

� All Methodologies/Delivery Approaches, techniques and practices have pros

and cons

� No silver bullet

Methodology/Lifecycle – Verb

“Waterfall” Methodology/Lifecycle

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

� deliverables/artifacts defined, assigned, and documented

� formal structure required

“Agile” Methodology/Lifecycle

� one or several iterations through a methodology/lifecycle (noun)

� limited deliverable creation

� formal structure not required

QAIassist Integrated MethodologyWaterfall








QAIassist Integrated MethodologyAgile, Spiral, RAD, Prototyping

























Recap


Agenda








Recap


Agenda

SDLC Fundamentals - 101

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

SDLC Fundamentals - 102

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

Not every deliverable of every lifecycle 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

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

®

®

V Diagram

Mainframe, Distributed, Web Based

Waterfall, Agile, Prototyping

Integration








Recap


Agenda








Recap


Agenda

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

� Maintain and accurately document the approved/authorized requirements through the life of

the project

� 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

Software Development Lifecycle (SDLC)

Phases

SDLC objectives (see previous page) are achieved utilizing five phases,

they are :

� Systems Analysis

� Design

� Build

� Test (Unit)

� Release

QAIassist Integrated MethodologyWaterfall, Agile, Spiral, RAD, Prototyping



QAIassist Integrated MethodologyWatefall, Agile, Spiral, RAD, Prototyping



SDLC – Systems Analysis Phase

Objectives

� ensure a formal project exists and has been authorized (Business Case established)

� project team members review and understand project context (deliverables)

� identify/refine initial business requirements

� establish high level design

� establish Requirements Traceability Log

Iterations

� iterative within the phase (waterfall)

� iterative within the lifecycle (agile)


SDLC - System Analysis Phase

(Entry Deliverables)

Business Case (entry)

Used to identify, document and establish a project definition. It originates out of a

business need and acts to provide a high level description of the business

requirements. It is used as an entry point into the QAIassist Integrated Methodology

(project management, software development, software testing) and is referred to

throughout the life of the project.

Project Charter (entry – created in PM lifecycle)

Used to establish a formal project. It is the initial deliverable prepared for a project

and defines why the project was initiated, the scope of the project, the purpose &

objectives of the project, the project milestones and a high level estimate on the

effort and cost associated with the project. The Project Charter acts as the “footing"

for the project.


(Exit Deliverables)

Detailed Business Requirements (exit)

Used to provide clarity on the business need that is to be addressed. It provides the

project team the business parameters (operational, administrative, technical) they

will use to deliver the necessary business functionality.

High Level Solution Design (exit)

Used to define the boundaries of the application to be delivered. It illustrates the

data and the process flows, the high level functionality (operational, administrative,

technical) to be incorporated into the application, the sub-systems and functions

required to satisfy the business needs of the application, and the standards to be

applied in developing the application.


(Exit Deliverables)

Requirements Traceability Log (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.



SDLC – Design Phase

Objectives

� ensure the application is designed in accordance with the authorized requirements

defined during the System Analysis phase

� complete the design of the application

� create specifications that reflect the authorized design & business requirements

� maintain Requirements Traceability Log

Iterations




SDLC - Design Phase

(Exit Deliverables)

Detailed Solution Design Requirements (exit)

These deliverable(s) are an extension of the High Level Solution Design deliverable - each function as

defined in the High Level Solution Design deliverable is further clarified with a separate and unique

Detailed Solution Design deliverable. Each of the Detailed Solution Design deliverables address the

necessary functionality (operational, administrative, technical) to be incorporated into the application,

identifies the specific application program/modules that will provide that functionality, and establishes the

interfaces with other application functions.

Programming Specifications (exit)

These deliverable(s) are an extension of the Detailed Solution Design deliverables - each “technical”

program/module (not operational, not administrative) defined in a Detailed Solution Design deliverable is

further clarified as a unique Programming Specification deliverable. Each Programming Specification

deliverable defines the purpose and context for the program/module, the environment it will operate in,

the detailed design to be incorporated into the program/module and the functionality to be delivered by

the program/module.

SDLC - Design Phase

(Exit Deliverables)


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


environment.



SDLC – Build Phase

Objectives

� develop the required functionality according to the authorized design and business

requirements

� create unit code of the application according to the programming specifications

� develop the User Training and Support Plan


Iterations




SDLC - Build Phase

(Exit Deliverables)Unit Code (exit)

The code is developed/generated from the Programming Specification(s)

deliverables (one per module/program). The code will incorporate the technical

standards and all the necessary functionality as defined by the business

requirements for each program/module.

User Training & Support Plan (exit)

This deliverable provides the description of how the end users are going to be

trained in using the final application/product and the support they will receive once

the application/product has been made operational. It specifies the methods of

training, the curriculum, the course(s) contents and the particulars associated with

delivering the training.

SDLC - Build Phase

(Exit Deliverables)


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


environment.



SDLC – Test PhaseObjectives

� perform all unit testing according to Unit Test Plans (from STLC)

� ensure the application/product has been built in accordance with the authorized design,

business requirements, Unit Test Evaluation Criteria (from STLC)

� identify and address all conditions that do not satisfy unit test testing criteria

� ensure all unit testing deliverables/work products are under configuration management


Iterations




SDLC - Test Phase

(Entry Deliverables)Unit Test Plan(s) (entry - created in STLC)

– These deliverables (one per program/module) define how all of the unit testing activities are to be

executed prior to the application/product being migrated into the System Integration Test

environment. They identify the testing tasks to be completed in the UT environment, the testing

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

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

Unit Test Evaluation Criteria (entry - created in STLC)

– These deliverables (one per program/module) are used to document the "expected" Unit Test

evaluation criteria prior to conducting the Unit Testing. This criteria is used to evaluate “expected”

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

the System Integration Test (SIT) environment. Functionality that "fails" these Unit tests are

recorded and require further activity from the project team.

SDLC - Test Phase

(Exit Deliverables)Unit Test Defect Log (entry - exit)

– The Unit Test (UT) Defect Log(s) is used to document and monitor all of the "failed"

tests against the Unit Test Evaluation Criteria deliverable. Each "failed" test is

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

necessary changes to rectify the "failed" test.

Unit Test Authorization (exit)

– This deliverable signifies “approval” that all project unit coding, deliverables and

work products have satisfied the Unit Test Evaluation Criteria and can be migrated to

the System Integration test environment. Approval of this deliverable ensures all

unit testing deliverables, work products and artifacts are placed under proper

configuration management and can be used as the basis for further testing.

SDLC - Test Phase

(Exit Deliverables)


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


environment.



SDLC – Release Phase

Objectives

� authorize that all necessary “unit” testing is complete - promote the newly built and

unit tested functionality/application for additional testing

� ensure all unit testing deliverables and work products under configuration management


� migrate the application for additional (SIT, UAT) testing

Iterations




SDLC - Release Phase

(Exit Deliverables)Unit Test Authorization (exit)

This deliverable signifies “approval” that all project unit coding, deliverables and work

products have satisfied the Unit Test Evaluation Criteria and can be migrated to the

System Integration test environment. Approval of this deliverable ensures all unit testing

deliverables, work products and artifacts are placed under proper configuration

management and can be used as the basis for further testing.

Unit Code (exit)

The code is developed/generated from the Programming Specification(s)

deliverables (one per module/program). The code will incorporate the technical

standards and all the necessary functionality as defined by the business

requirements for each program/module.













Recap


Agenda








Recap


Agenda

SDLC - “Project” Benefits

On Time – project teams are able to scale and

leverage the phases and deliverables to

effectively deliver projects and functionality

Within Budget – familiarity and recurring usage

provides project teams a tool they can reuse to

consistently deliver applications within budget

Built In “Quality” – structure ensures project

teams are working on the right deliverables for

the right reasons to deliver the right solutions

Common IT Process – applying a

methodology /lifecycle to IT development

and maintenance activities contributes to a

standard organizational approach (adhering

to budget, schedule, quality, resource

flexibility)

Quality Assurance & Governance – applying

a methodology/lifecycle provides the basis

for organizational process management -

verifying and evaluating how organizational

staff are utilizing the process

Metric – Basis for Improvement – applying

an organizational methodology/lifecycle

provides the basis for assessing its usage and

how it can be approved upon

SDLC - “Process” Benefits








Recap


Agenda








Recap


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 (Janelle 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 a certified QAIassist

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

2014 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 (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.

2014 “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)

2014 “Concepts” Schedule

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



� 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)

Denise Rodriguez

Project Insight

Marketing

[email protected]

www.projectinsight.net

Twitter: @projectinsight

Moderator

Documents

IT Methodology Webinar - Project Insightdownloads.projectinsight.net › training › it-methodology...2014 Schedule The 3rd Wednesday of Every Month 8:00 am Pacific -11:00 am Eastern