Telephone: (215) 716-7373


Home » Team Building » The Application & Network Performance Analysis Team (NAPA)™


The Application & Network Performance Analysis Team (NAPA)™

Bookmark and Share

Cutting Through Opinions
Diagnosing Facts
Providing
Resolution


Click Here to Listen to this topic as a "The ROOT Cause" podcast.  

 

Click Here to Subscribe through

 

Click Here to Subscribe through  


INTRODUCTION:

Application & Network  Performance Analysis is a team sport.  Rarely are all the required skills in one skull.  Perhaps it is best understood once you think in terms of functions and skill-sets within a Troubleshooting process.  In order to be able to handle ANYTHING that comes along, you will need team members with high level skills in Enterprise Applications--Operating Systems--Databases--Server Issues and a detailed understanding of Protocols and Packet-Level transactions.   But, to expect one or two people to have detailed knowledge of all these areas is unrealistic.

The Senior Network and Application Performance Analyst (NAPA)™ will need to be able to communicate with all these individuals, teams and managers.  Communication & interviewing abilities are mandatory.   If, even by some chance, you have the world’s best troubleshooter--what if they leave?  This Team approach is practical and stable.

 THE 7 PRIMARY TEAM ROLES:

 1) Network & Application Performance Analyst (NAPA)™

Team Manager & Technical Team Lead.  The NAPA must learn all the Client’s goals - Technical - Political - Management - Budgetary -scales the team accordingly.

This person needs to understand all the various technical issues and be able to discuss them and ask the right questions of the individual experts.  They are the hub of the team's wheel.

 2) Enterprise Application Specialist (EAS)

Able to map Application flow from functional & transaction basis. Understands Database interactions - Multi-Tiered Architecture - Web Servers

 3) Protocol Analyst - Packet-Sniffer Guru.

Understands Network Protocols - Topology Framing - Troubleshooting from the Packet Level. 

This individual will be capturing trace files and analyzing the traffic at the protocol and packet-level.

 4) Network Engineer

Familiar with wide variety of vendors i.e. Cisco--Foundry-- Nortel--Troubleshooting Layers 1-3. 

If this team member is part of an in-house team, they need only be up to date on the manufacture’s equipment in place within your organization.  However, if your team is a consulting team...this individual has to have experience with a wide range of manufactures.

 5) Operating Systems Specialist

UNIX & Windows, Other...

 6) Project Manager

Maintains Task List - Gant Chart - Reports to Client's Management

 7) Technical Writer

Creates deliverable documentation showing work & resolutions provided by Network Application Performance Analysis Team. 

This person does not need to have a solid technical understanding but must be able to follow the gist of it when interviewing the technical team in order to "translate" the information into a document that is understandable to both a technical and NON-technical reader.

Network & Application performance Analysis troubleshooting doesn't require separate people in each role - single individuals can perform multiple roles.   The Senior NAPA may be able to perform all roles--at a high level.  However, the Client’s Subject Matter Experts (SME) will still be required.  Consider them a guest member of the team.

FREQUENT ROLE COMBINATIONS:

 · Project Manager — Technical Writer

 · Network & Application performance Analysis — Protocol Analysis 

 · EAS — Operating System Specialist

INITIAL STEPS:

 1)  NAPA meets with Client Management - determines goals.

 2)  EAS meets with Application Subject Matter Experts (SME) - begins to map out the Interpath.

 3)  NAPA gathers all applicable documentation - begins environmental overview.

 4)  NAPA- EAS determine test goals.

 5)  NAPA- EAS - Client SME design test plan - select test transactions.

 6)  NAPA- Network Engineer - Client Network SME.

 7) Map out Interpath within Network Infrastructure.

 8) Plan how to place Sniffer, Ethereal - WireShark. Mirrors (SPANs) - Taps - Host Based - Wire Speed, etc.

 9)  Implement plan & deploy tools.

10) Protocol Analyst - NAPA executes selected Application Transaction for performance analysis - captures appropriate trace files - log User experience.

11) Protocol Analyst performs analysis of trace files & begins Documentation.

12) Theories are developed - Test Plan modified - second round of analysis testing (where needed).

Having a Champion within Client's organization is critical.  Organization's staff is not accountable to NAPA Team - does not have to provide information or perform tasks. Will not do so when busy - but always busy!  Clear path of internal escalation & champion provides authority.

For full article and more information on this topic, Click Here.




Related Topics:


Back to main topic: Team Building
Resolution is the Primary Goal
The Missing Link in IT Management
Mentoring in IT
Testing Enviroments--Cost Justification
The Technical Enterprise Practitioner (TEP)™
The New Information Technology Marketplace
The Ethical Conflicts Created by MBO Incentive Programs
Consulting Compared to Being an Employee - Part One
Horizontal Knowledge and Vertical Knowledge in the IT World
Inter-Silo Communication in IT Organizations

Subscribe to receive the latest news & specials on our products:

Quick Find
 
Use keywords to find the product you are looking for.
Advanced Search

Articles
New Articles
All Topics
 Application Architecture
 Case Studies
 NetAnalysis Myth Series
 Podcasts
 Team Building
 Troubleshooting
Articles RSS Feed
Information
Shipping & Returns
Privacy Notice
Conditions of Use
Newsletter
Contact Us
Catalog Feed

Copyright © 1999-2013 Barry Koplowitz