5. QA Staffing Level The skills of a capable QA group are essential to improving application development & maintenance: Early discovery of inconsistencies Errors reduce Rework prevention Yet, the appropriate level of QA staffing is often difficult to determine
6. Factors Influencing QA Staffing Level When ITO requires higher level of QA staffing: Orgs that produce their own SW other than orgs that implement commercial SW packages Orgs relying on SW for mission-critical functions Highly regulated industries Orgs that produce SW as a part of their services to customers Companies devoting their efforts to steady process improvement (Six Sigma/ CMMI…)
9. Find The Right Balance Too often QA is viewed as an obstacle to getting work done Desire to meet deadlines & enhance systems Need to ensure quality, reduce waste & enforce standards
10. IT Trends Influencing QA Staffing Level New regulations Cloud computing Office of the CIO Agile Outsourcing Agile
11. New Regulations Requirements In recent years, the quality & integrity of information systems are being examined more closely because of regulations that address the security and privacy of information QA function becomes even more important in light of these requirements
13. Office of the CIO Israeli Trends After many years of talking OTC is actually happening! Financial crisis & budget reduction in 2009 forced better ITG: Increased focus on IT costs - efficiency increasing New regulations requested better transparency Most ITOs have expanded their OTC/ PMO department: IT budget control & mng, PPM, rewrite methodologies & WF definition, tools evaluation, HR - resource allocation & mng, QA, GRC…
14. The PMO goals are: Keep all this in the right balance: Scope of Work Budget Time Quality
15. SW Development Metrics Bugs - How many bugs (including severity) When the bug was open, when it was closed Number of bugs correspondingly to closing date of the version When was the bug found(dev, functional test, regression, prod = escaping bugs) Test coverage (what part of SW was tested) Percentage of automatic tests (from the complete project = automatic + manual) Progress of project compared to plan How many (and percentage of) passed builds Development of new functionality vs. effort to correct bugs from prod & from tests STKI recommends: change your metrics once in a while
16. SW Measurement Insights Bugs are the most easy metric to measure & track Sometimes too much effort is spent on bugs (example: minor memory leak) while important functionality is delayed How much effort should developer put in “non-dev” missions (like detailed progress report)? Should maintenance be part of the general development team or should maintenance have a special “team”?
18. Traditional Software Development The traditional development focus is to engineer out defects Good principle Hammer out defects early Defects arise because requirements change Too many communication gaps Design Code Test Deploy Isolated Process 18
19. Agile Project Management 12 9 6 3 12 3 6 9 Code Analysis Code Test Implement Test Analysis Work Effort Source: Cutter Time in Months
20. Agile SW Development Israeli Trends Agile is catching up in ITOs Clients see the benefits of Agile in SMPs Large Agile projects (50 people) are more challengeable mainly when there is high interdependencies between the SW modules Israeli ISV’s report that sometimes their clients demand Agile Agile requires change in the hierarchical structure that is extremely difficult to large conservative organizations
22. Outsourcing While Professional Services market significantly dropped last year, the QA & testing PS remained stable QA - rapidly growing sourcing segment Acknowledging the advantage & cost saving (up to 50%) by local nearshore
23. Israeli Nearshore Israeli ITOs do not offshore QA, except global orgs Israeli nearshore existing clients have broaden their scope Added Value Professional Services : Best Practices – ISTQB, ISO 27001 Automation Testing Tools ISTQB COBIT CMMI ISO Six Sigma
24. Israeli Nearshore Main Players Matrix Global (Talpiot) Ness Malam Team Ness Aman – Tehila Manpower Galil Software Many more…
25. Pricing Models Traditionally QA was priced on a fixed-time/fixed-price basis (most tenders still are) Today: There is a real difficulty to evaluate QA scope of work, therefore most contracts priced on time & material basis Israeli ITOs prefer in-house responsibility & QA PS, both On premises Off premises – nearshore
26. Developers vs. Testers Advantage: Already knows the system - Driven by “delivery” Disadvantage: Must learn the system - Seek the problems - Driven by “hours” But But
בוקר טוב וברוכים הבאים לכנס השנתי של STKI. שמי גלית פיין ואני אנליסטית בתחום של OFFICE OF THE CIO. השנה, בנוסף לנושאים הרגילים של OFFICE OF THE CIO, אני אתמקד במגמות המובייל, מכיוון שלשימוש העולה בטלפונים הסלולאריים החכמים יש השפעות חברתיות וכלכליות מרחיקות לכת. ואמנם החלטות המובייל מתקבלות ברמה הארגונית - אנו מעריכים, כי לארגוני IT יהיה תפקיד מכריע בשינוי מודלים עסקיים מסורתיים הן לגבי האינטרקציה עם הלקוחות והן לגבי צורת העבודה של אנשי השטח בארגון.
