IT Methodology Webinardownloads.projectinsight.net/training/it-methodology-webinars/... · 2013 Schedule The 3rd Wednesday of Every Month 8:00 am Pacific -11:00 am Eastern Time IT

IT Methodology Webinar

Incorporate Organizational Process Governance

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

Janelle Abaoag

Project Insight

Marketing, Public Relations

[email protected]

www.projectinsight.net

@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?

Scores of IT Methodology Webinars delivered (across the globe)

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

2012/13 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 2012/2013 Series - Goals

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

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

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





















Concepts V

Incorporate Organizational Process GovernanceAgenda

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

� IT Methodology (noun) - “Project” versus “Organizational Process”

� “Organizational Process” Characteristics (repeatability, predictability, measurability)

� “Organizational Process” Benefits (corporate planning, staffing

flexibility/opportunity, consistent delivery & quality, accountability, continuous

improvement)

� “Organizational Process” Implementation Considerations

� Recap

Concepts V







improvement)


� Recap

� 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


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

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, 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

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

IT Methodologies – Utility

Multiple IT Environments :

� Mainframe

� Distributed

� Web Based

Multiple Delivery Approaches – Methodology (verb)

� Waterfall

� Agile

� Prototyping

IT Methodologies – Business Context

Development Environment

� New Products

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

Maintenance/Support Environment

� Existing Products

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

� Off the Shelf Applications

Concepts V







improvement)


� Recap

Concepts V







improvement)


� Recap

“Project” Context






Project ManagementMethodology/Lifecycle

“Project” - Project Management Context(singular project usage)

Objectives

� Establish Project

� Plan (Resources, Deliverables, Activities,

Quality, Risk)

� Execute & Control (Plans)

� Deliver to Users on Time and Budget

Audience/Roles

� Business Stakeholders


� Business Analysts

� System Architects & Analysts

� Programmers & Testers

� End Users



Software Development Methodology/Lifecycle

“Project” – Software Development Context(singular project usage)

Objectives

� Enhance project team communications

� Define formal user requirements

� Design solution to satisfy user

requirements

� Build desired functionality

Audience/Roles



� Business Analysts & Architects


� End Users



Software Testing

Methodology/Lifecycle

“Project” – Software Testing Context(singular project usage)

Objectives

� Enhance project team communications

� Enable testing activities to begin from

project startup

� Correlate expected and authorized

requirements with application being

delivered

� Users verify final solution

Audience/Roles



� Business Analysts & Architects


� End Users

“Project” (singular project usage)

Lifecycles

� Project Management

� Software Development

� Software Testing

Benefits

� Planning, Executing, Delivering

� Requirements Definition, User

Approval

� Successfully Tested Authorized

Functionality

“Project” Context

“Process” Context

“Process” (all organizational project usage)

Lifecycles




Benefits

� Planning, Executing, Delivering

� Requirements Definition, User

Approval

� Successfully Tested Authorized

Functionality

Concepts V







improvement)


� Recap

Concepts V







improvement)


� Recap

“Organizational Process”Characteristics

Lifecycle/Process




Characteristics

� Repeatability

� Predictability

� Measurability

Organizational “Process” Characteristics Repeatability

Lifecycle/Process




Results

� Specific tasks, and work products

(deliverables) pre-defined

� Projects are regularly delivered on time and

within budget

� Quality is inherent in the process and the

product/service being delivered

Organizational “Process” Characteristics Predictability

Context




Results

� Specific roles and responsibilities are pre-

defined

� Product/Service delivery more reliable

� Corporate planning (budgeting and staff

forecasting) becomes more reliable

Organizational “Process” Characteristics Measurability

Context




Results

� Repeatable & Predictable = Measureable

� Measurable = Basis of Ongoing Improvement

� Ongoing Improvement = Operational

Performance and guaranteed Quality (product

& process)

Concepts V







improvement)


� Recap

Concepts V







improvement)


� Recap

Organizational “Process” Benefits

Corporate PlanningContext




Benefits

� Establishes benchmark of operational

capacity

� Benchmark of operational capacity

utilized for strategic and intermediate

(budget and staff) planning


Staffing Flexibility and Opportunity

Context




Benefits

� Transportable Skills

� Variability of Environment

� Exposure to cross functional business

functions and applications

� Career Evolution


Consistent Delivery & Quality

Context




Benefits

� Repeatable process efficiency

� Verifiable utilization ensures process

has been applied – results in delivery

of quality in product/service


Accountability

Context




Benefits

� Predefined Operational Roles

� Predefined benchmark for evaluation

� Formal review and audit of process

� Feedback mechanism for resource

evaluation


Continuous Improvement

Context




Benefits

� Process can be measured/metrics

� Metrics can be evaluated and utilized

to revise/enhance process

� Corporate Maturity - Cultural

Concepts V







improvement)


� Recap

Concepts V







improvement)


� Recap

Implementation Considerations

Corporate Objectives� Governance – Organizations have developed and utilizing their corporate process(es) – these

organizations want to ensure the process(es) they have developed are applied effectively.

Specialized staff are dedicated to lead these initiatives (PMO) - process scope can vary

� Quality Assurance – Organizations have a belief that the quality of their products and services

rely and are dependent on how effectively the organizational process(es) are being followed.

Specialized staff are dedicated to perform ongoing process reviews and audits

� Continuous Improvement– Organizations recognize that operational performance (and

corporate culture) can be continually improved when the processes incorporate a metric

component. The metrics can be used to measure performance (schedule, cost, quality) of how

the products/services are being developed and delivered. Dedicated resources are used to

acquire and disseminate metric information to operational management


Scope – Existing Corporate MaturityEvery organization is using a process ( IT Methodology or IT Lifecycle or IT

Framework) to deliver products and/or services

� Optimized – IT Methodology is recognized and aligned with business objectives and routinely

delivers to operational needs and expectations – metrics for continuous improvement

� Maximized – IT Methodology is recognized and aligned with business objectives and regularly

delivers to operational needs and expectations – no metrics for continuous improvement

� Utilized – IT Methodology is recognized yet inconsistently applied resulting in deviations

(schedule, cost, quality) of the products/services being delivered

� Chaotic – IT Methodology is not recognized, process(es) are not applied


Cornerstones for SuccessEstablish Ownership/Steering Committee – have a champion

Identify and designate “process” experience/expertise (in-house/other) – experience

matters

Identify the scope of the process/methodology (ie Project Management, Software

Development, Software Testing) or phase or deliverables that will bring value once

implemented – define the piece of pie

Designate the initiative as a project – apply PM practices (initiate, plan, execute & control,

closeout) to guide the project implementation

Continuous communication (across the organization) from process development through

process training through process implementation

Concepts V







improvement)


� Recap

Concepts V







improvement)


� Recap


Every IT organization is using an

IT Methodology or IT Lifecycle or IT Framework

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

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

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











Janelle Abaoag

Project Insight

Marketing, Public Relations

[email protected]

www.projectinsight.net

@projectinsight

Moderator

IT Methodology Webinardownloads.projectinsight.net/training/it-methodology-webinars/... · 2013 Schedule The 3rd Wednesday of Every Month 8:00 am Pacific -11:00 am Eastern Time IT

Documents