it methodology webinar - project insightdownloads.projectinsight.net/training/it... · pioneer of...
Post on 23-May-2020
6 Views
Preview:
TRANSCRIPT
Customize an IT Methodology for Your Organization
IT Methodology Webinar
Phones will be on mute
Ask your questions using your
GotoWebinar panel
Webinar recording will be
available in the Project Insight
Community
Before we get started…
Janelle Abaoag
Project Insight
Marketing, Public Relations
Janelle.Abaoag@projectinsight.com
www.projectinsight.net
@projectinsight
Moderator
Cameron Watson
President, QAIassist
cwatson@qaiassist.com
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?
Eleven (11) 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 Consultants
IT Methodology Webinar Summary
2012 Schedule
The 3rd Wednesday of Every Month
� 8 :00 Pacific Time, 11:00 Eastern Time
IT Methodology Modules
� Integrating Methodologies into an IT Landscape (Jan 2012)
� Crossing IT Methodology Over Organizations (Feb 2012)
� Why Use a PM Lifecycle & Deliverables (Mar 2012)
� Apply PM Fundamentals for a Successful Project (Apr 2012)
� Scale PM Deliverables to Benefit Your Projects (May 2012)
� Consistently Improve Your Organizational Processes (Jun 2012)
� Why Use a Software Development Lifecycle (Jul 2012)
� Apply the Software Development Lifecycle for a Successful Project (Aug 2012)
� Why Use a Software Testing Lifecycle (Sept 2012)
� Apply the ST Lifecycle for a Successful Project (Oct 2012)
� Customize an IT Methodology for Your Organization (Nov 2012)
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 Series - Goals
Module XI - Customize an IT Methodology
for Your Organization
IT Methodology – general context
IT Methodology – “project” versus “process”
IT Methodology - Implementation Considerations
IT Methodology - Implementation Guidelines
Recap
IT Methodology – “Known”
The term “Methodology” originates in ancient Greece from the
word “Methodos” - meaning “path”
Although Business Leaders, Engineers, Scholars have long
debated and argued over which methodologies are the most
effective – all are in agreement that employing any
methodology is always beneficial
Every organization is using an IT Methodology or IT Lifecycle or
IT Framework
in partnership with
� 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
� Deliverable, Artifact, Work Product
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
Organizational Frameworks
ISO (xxx)
� Largest developer and publisher of international standards, multiple frameworks
including
9001 – Quality Management, 14001 – Environmental Management
SEI/CMMI
� Software Engineering, computer security, organizational process management and
improvement
Six Sigma
� Improve the quality of business and manufacturing process outputs by identifying
and removing the causes of process defects (errors) and minimizing variability
Organizational Frameworks
ITIL
� Aimed at aligning IT services with business objectives, widely used approach for IT
Service Management – service desk, application management, IT operations,
technical management
COBIT
� Helps IT professionals and enterprise leaders fulfill their IT governance and
management responsibilities
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
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
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
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
IBM’s Rational Unified Process (RUP)
PMI’s Project Management Methodology
QAIassist Integrated Methodology
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
IT Methodologies - Noun
IBM’s - Rational Unified Process (RUP)
� Iterative and complex software development process used by large sized organizations to
develop software
PMI & PMBOK
� Create and maintain standards that provide processes, guidelines, rules and characteristics for
project management (US based)
Prince2
� Structured Project Management Method endorsed by the UK government as the project
management standard for public projects (UK based)
QAIassist
� Integrated (project management, software development, software testing) IT methodology used
by small and mid sized businesses to develop and support products and business applications
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
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
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
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 a software development and testing
methodology/lifecycle (noun)
� deliverables/artifacts/work products are defined, assigned, documented and
maintained
� More formal structure required for execution
“Agile” Methodology/Lifecycle
� multiple iterations through a software development and testing
methodology/lifecycle (noun)
� limited deliverable creation – limited documentation
� less formal structure required for execution
QAIassist Integrated Methodology
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
Frameworks, Methodologies, LifecyclesCommonalities
� All viable IT related frameworks/methodologies/lifecycles (noun),
methodologies/lifecycles(verb) originated out of a need to increase/improve
productivity - all based on helping not hindering
� All viable IT related frameworks/methodologies/lifecycles (noun), and
methodologies/lifecycles (verb) have been designed to support the delivery of
organizational products and/or services
� Each viable IT related framework/methodology/lifecycle (noun), and
methodology/lifecycle (verb) was created to address and support a strategic or
operational goal (ie ISO versus CMM versus PMI versus Agile versus QAIassist)
� Correlation exists between the usage of a viable IT
framework/methodology/lifecycle (noun), methodology/lifecycle (verb) and an
organization’s ability to repeatedly deliver quality IT
products/applications/functionality on time and within budget
Module XI - Customize an IT Methodology
for Your Organization
IT Methodology – general context
IT Methodology – “project” versus “process”
IT Methodology - Implementation Considerations
IT Methodology - Implementation Guidelines
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
IT Methodology/Lifecycle
“Project” versus “Process”
Project
� Applying the methodology (noun - project management, software
development, software testing) and/or (verb – agile, spiral, waterfall, etc)
on a unique project by a designated team to deliver a specific solution
Process
� Applying the methodology (noun - project management, software
development, software testing) and/or (verb – agile, spiral, waterfall, etc)
on all organizational projects to establish a repeatable and reliable
process that can be measured and improved upon
QAIassist Integrated Methodology
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
� Project Managers
� Business Analysts
� System Architects & Analysts
� Programmers & Testers
� End Users
Project Management Methodology
“Project” Context - Benefits
On Time – project team is able to scale
and leverage the phases and deliverables
to effectively deliver their project and
functionality
Within Budget – project team will be able
to utilize the phases and deliverables to
deliver their project within cost and
budget expectations
Built In “Quality” – project team will rely
on the phases and deliverables to ensure
quality is incorporated into the solution
“Process” - Project Management Context(multiple project usage)
Objectives
� Establish repeatable (measurable) process –
deliver quality projects on time and within
budget
� Quality Assurance/Governance
� Ongoing Measurement and Improvement
Audience/Roles
� Project Owners/Corporate Stakeholders
� Project Teams
� Organizational PMO, QA, Governance
� End Users
Project Management Methodology
“Process” Context - Benefits
On Time – process enables all organizatonal
project teams are able to scale and leverage
the phases and deliverables to effectively
deliver projects and functionality
Within Budget – process establishes
familiarity and recurring usage provides
project teams a tool they can rely to
consistently deliver applications within
budget
Built In “Quality” – process establishes a
benchmark that acts as a basis for review and
ongoing improvement
Software DevelopmentMethodology/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 Stakeholders
� Project Managers
� Business Analysts
� System Architects & Analysts
� Programmers & Testers
� End Users
Software Development Methodology
“Project” Context - Benefits
Communication – project team members
(Business and IT) utilize the phases and
deliverables to speak the same language
Requirements Definition – project team
(Business and IT) rely on the phases and
deliverables to ensure the business need is
articulated and agreed upon
Design & Construction – project team
(Business and IT) leverages the agreed
upon requirements to design, construct
and deliver the necessary functionality
“Process” – Software Development Context(multiple project usage)
Objectives
� Establish repeatable (measurable) process –
deliver quality projects on time and within
budget
� Quality Assurance/Governance
� Ongoing Measurement and Improvement
Audience/Roles
� Project Owners/Corporate Stakeholders
� Project Teams
� Organizational PMO, QA, Governance
� End Users
Software Development Methodology
“Process” Context - Benefits
On Time – process enables all project
teams are able to scale and leverage the
phases and deliverables to effectively
deliver projects and functionality
Within Budget – process establishes
familiarity and recurring usage provides
project teams a tool they can rely to
consistently deliver applications within
budget
Built In “Quality” – process establishes a
benchmark that acts as a basis for review
and ongoing improvement
Software TestingMethodology/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 Stakeholders
� Project Managers
� Business Analysts
� System Architects & Analysts
� Programmers & Testers
� End Users
Software Testing Methodology
“Project” Context - Benefits
Communication – project team members
(Business and IT) utilize the phases and
deliverables to speak the same language
Requirements Verification – project team
(Business and IT) rely on the phases and
deliverables to ensure the business need is
articulated and delivered
User Authorization – User Community
verifies solution prior to application being
used in production environment
“Process” – Software Testing Context(multiple project usage)
Objectives
� Establish repeatable (measurable) process –
deliver quality projects on time and within
budget
� Quality Assurance/Governance
� Ongoing Measurement and Improvement
Audience/Roles
� Project Owners/Corporate Stakeholders
� Project Teams
� Organizational PMO, QA, Governance
� End Users
Software Testing Methodology
“Process” Context - Benefits
Testing a Priority – project team initiate
testing activities as requirements are
defined and agreed upon (no throwing
over the fence at the 11th hour)
Pre-defined Test Criteria – project team
establishes testing criteria (according to
documented and agreed upon
requirements)
Validated Release – release of application
into a production (user) environment is
dependent on all predefined test criteria
being satisfied
Module XI - Customize an IT Methodology
for Your Organization
IT Methodology – general context
IT Methodology – “project” versus “process”
IT Methodology - Implementation Considerations
IT Methodology - Implementation Guidelines
Recap
Implementation Considerations every organization is unique
What is the nature of the existing business and associated business factors ?
� products, services, speed to market, quality, cost/revenue
What is the motivation – why implement an IT methodology (noun or verb)?
� regulatory, contractual, quality, efficiency, resource flexibility
Have previous organizational implementation efforts been attempted – were
they successful ? Why or why not ?
Scope - amount of effort and resources required to implement – how big a
slice of pie is required ?
Should the designated implementation be to a “project” or as a “process” ?
QAIassist Integrated Methodology
Implementation Considerations Organizational Maturity
Every organization is using a process ( IT Methodology or IT Lifecycle or
IT Framework) to deliver products and/or services
� Optimized – process(es) are recognized and aligned with business objectives and
routinely delivers to operational needs and expectations – metrics for continuous
improvement
� Maximized – process(es) are recognized and aligned with business objectives and
regularly delivers to operational needs and expectations – no metrics for
continuous improvement
� Utilized – process(es) are recognized yet inconsistently applied resulting in
deviations (schedule, cost, quality) of the products/services being delivered
� Chaotic – process(es) are not recognized, process(es) are not applied
Optimized
Maximized
Utilized
Chaotic
None of the above
Implementation Considerations looking into the mirror
Implementation Considerations value = how big a slice of pie ?
Is there an existing industry recognized framework/methodology (noun or
verb) that can be leveraged as the basis/criteria for guiding implementation ?
� ISO, SEI/CMMI, COBIT, PMI, Prince2, QAIassist
Is there a specific operational bottleneck or inefficiency that can be address
immediately ?
� Project Management, Software Development, Software Testing
Is there a specific phase, deliverable or activity that can be used to alleviate
the bottleneck of inefficiency ?
� Project Charter, Business Case, Testing Strategy, Project Plan, Requirements
Traceability Matrix, User Acceptance Test Criteria, Unit Test Plan
Module XI - Customize an IT Methodology
for Your Organization
IT Methodology – general context
IT Methodology – “project” versus “process”
IT Methodology - Implementation Considerations
IT Methodology - Implementation Guidelines
Recap
IT Methodology ImplementationSuccess Factors
Effective and engaged organizational ownership
� Designated owner ensuring project management (plan, schedule, roles, risks, etc) is
being applied
� Ongoing initiative for improvement
Designated resources required for implementation
� Designated resources (Project Team, PMO, Training)
Designated resources for ongoing support and improvement
� Designated resources (Management, Governance/QA, Metrics)
IT Methodology Implementation ABC’s of Implementation
Establish Ownership/Steering Committee – find a champion
Identify and designate “process” experience/expertise (in-
house/other) – experience matters
Identify the scope of the methodology (ie Project Management,
Software Development, Software Testing) or phase or deliverables that
will bring value once implemented
Designate the initiative as a project – apply PM practices (initiate,
plan, execute & control, closeout) to the project
Continuous communication (across the organization) from
development through training through implementation
IT Methodology Implementation ABC’s of Implementation (continued)
Develop and deliver a training curriculum and all required/associated
courseware – maintain attendance records when delivering training
Establish necessary operational structure/roles that will be used to
support and maintain the implementation
Consistently monitor and report the status of the implementation
schedule with Owner and Stakeholders
Actively address and pursue “process” non-compliance with Owner
and Stakeholders
Implementation Considerations Deterrents/Risks/Hiccups
Ongoing discussions, dilemmas and debates
� internal resistance (old way is the best way)
� no time for training, limited “process” support available
� staff seeking clarity of priority – operations vs implementing new processes
� lack of training materials or verification that required training has been delivered
� process reviews and audits not scheduled as part of regular operations
� no oversight mechanism to address process “non-compliance”
� no process metrics recorded or distributed
� limited Project Management (plan, schedule, roles, procedures, issues, etc) applied
� no ongoing or accurate corporate implementation status provided to Corporate
Owner/Stakeholders
Module XI - Customize an IT Methodology
for Your Organization
IT Methodology – general context
IT Methodology – “project” versus “process”
IT Methodology - Implementation Considerations
IT Methodology - Implementation Guidelines
Recap
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
2012 Schedule
The 3rd Wednesday of Every Month
� 8 :00 Pacific Time, 11:00 Eastern Time
IT Methodology Modules
� Integrating Methodologies into an IT Landscape (Jan 2012)
� Crossing IT Methodology Over Organizations (Feb 2012)
� Why Use a PM Lifecycle & Deliverables (Mar 2012)
� Apply PM Fundamentals for a Successful Project (Apr 2012)
� Scale PM Deliverables to Benefit Your Projects (May 2012)
� Consistently Improve Your Organizational Processes (Jun 2012)
� Why Use a Software Development Lifecycle (Jul 2012)
� Apply the Software Development Lifecycle for a Successful Project (Aug 2012)
� Why Use a Software Testing Lifecycle (Sept 2012)
� Apply the Software Testing Lifecycle for a Successful Project (Oct 2012)
� Customize an IT Methodology for Your Organization (Nov 2012)
2013 Schedule
The 3rd Wednesday of Every Month
� 8 :00 Pacific Time, 11:00 Eastern Time
IT Methodology Modules
� Integrating Methodologies into an IT Landscape (Jan 2013)
� Crossing IT Methodology Over Organizations (Feb 2013)
� Why Use a PM Lifecycle & Deliverables (Mar 2013)
� Apply PM Fundamentals for a Successful Project (Apr 2013)
� Scale PM Deliverables to Benefit Your Projects (May 2013)
� Consistently Improve Your Organizational Processes (Jun 2013)
� Why Use a Software Development Lifecycle (Jul 2013)
� Apply the Software Development Lifecycle for a Successful Project (Aug 2013)
� Why Use a Software Testing Lifecycle (Sept 2013)
� Apply the Software Testing Lifecycle for a Successful Project (Oct 2013)
� Customize an IT Methodology for Your Organization (Nov 2013)
2013 – IT Methodology“Advanced” Schedule
Dates (TBD)
� Bi-monthly – duration (45 minutes)
� 8 :00 Pacific Time, 11:00 Eastern Time
IT Methodology Advanced – Modules
� Project Team Structure – Roles & Responsibilities (Feb 2013)
� Requirements Management (Apr 2013)
� Project Planning (May 2013)
� Project Tracking and Oversight (July 2013)
� Software Quality Assurance (Sept 2013)
� Software Configuration Management (Nov 2013)
Janelle Abaoag
Project Insight
Marketing, Public Relations
Janelle.Abaoag@projectinsight.com
www.projectinsight.net
@projectinsight
Moderator
top related