Top Banner
Quality Quality Management & Management & Control Control July 2014 July 2014 Maia Reshef Maia Reshef
16

Quality Control Proposal

Jun 23, 2015

Download

Software

Maia Reshef

Different aspects in quality control and management in software development and project management
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: Quality Control Proposal

QualityQualityManagement & Management &

ControlControl

July 2014July 2014

Maia ReshefMaia Reshef

Page 2: Quality Control Proposal

AgendaAgenda

Code Management and ControlCode Management and Control Quality Management and ControlQuality Management and Control Personal Case StudiesPersonal Case Studies

Page 3: Quality Control Proposal

Code Management and Code Management and ControlControl

Page 4: Quality Control Proposal

The Spaghetti Code ProblemThe Spaghetti Code Problem

Waste of valuable R&D timeWaste of valuable R&D time: : Rewrite old code instead of maintenance to existing Rewrite old code instead of maintenance to existing

code (veterans leave, new people arrive)code (veterans leave, new people arrive) High cost to migrate old code to new High cost to migrate old code to new

platform/languageplatform/language Changes to code may step over old fixes that were Changes to code may step over old fixes that were

donedone

Page 5: Quality Control Proposal

CausesCauses

Thousands of code lines in logic not familiar to Thousands of code lines in logic not familiar to

all developers or multi logic environmentall developers or multi logic environment Quick & dirty code areas which need to be re- Quick & dirty code areas which need to be re-

written to match best practicewritten to match best practice Missing unified comments format in the codeMissing unified comments format in the code Missing guidelines for code documentationMissing guidelines for code documentation

Page 6: Quality Control Proposal

How to PreventHow to Prevent

Define coding guidelines (comments, structure etc)Define coding guidelines (comments, structure etc) Code reviews by peer developers to verify the format is Code reviews by peer developers to verify the format is

clear to allclear to all Code reviews to verify the quality of the code writingCode reviews to verify the quality of the code writing Keeping historical records: keeping track of which Keeping historical records: keeping track of which

changes were made, who made them, when they were changes were made, who made them, when they were made and whymade and why

Private developer workspaces ("sandboxes“) – unit test Private developer workspaces ("sandboxes“) – unit test before integrating code into the main code linebefore integrating code into the main code line

Server back up mechanism to keep track on check in’sServer back up mechanism to keep track on check in’s

Page 7: Quality Control Proposal

Quality Management and Quality Management and ControlControl

Page 8: Quality Control Proposal

Development wants to provide Development wants to provide the best product butthe best product but……

The blanket is too short: sales want to add to the code feature xyz, customers complain on abc functionality, previous product release contains 2 critical bugs not known yet to sales/customers, CTO wants to move to new UI and to launch a mobile app…

What do we do?

Page 9: Quality Control Proposal

Define a Clear Prioritization Define a Clear Prioritization ProcessProcess

Verify we are on the same page regarding the prioritiesVerify we are on the same page regarding the priorities Set a clear plan for the next week/monthSet a clear plan for the next week/month Set a plan for the next buildSet a plan for the next build Verify each player in the team knows his tasks and Verify each player in the team knows his tasks and

handshakeshandshakes

Page 10: Quality Control Proposal

Cost of Poor QualityCost of Poor Quality

Page 11: Quality Control Proposal

Cost of QualityCost of Quality

Page 12: Quality Control Proposal

Ways to Control QualityWays to Control Quality

Manage process gating : Manage process gating :

sales/product-> development-> testing-> integration-> sales/product-> development-> testing-> integration-> deployment/customer supportdeployment/customer support

Status reports to stakeholdersStatus reports to stakeholders Manage release notes for every new release deliveryManage release notes for every new release delivery Perform lessons learned to prevent repetition of past Perform lessons learned to prevent repetition of past

failuresfailures Testing beyond the “lamplight” – extreme values tests, Testing beyond the “lamplight” – extreme values tests,

regression tests, load tests etcregression tests, load tests etc Monitor customers’ KPIs to learn where to invest valuable Monitor customers’ KPIs to learn where to invest valuable

effortsefforts

Page 13: Quality Control Proposal

Personal Case studiesPersonal Case studies

Page 14: Quality Control Proposal

Case study 1:Case study 1: TMO project requiremTMO project requirements ts

Telecom Mobile EU (TMO) requirements were defined by the customer Telecom Mobile EU (TMO) requirements were defined by the customer representatives and sent over to the division after contract signature representatives and sent over to the division after contract signature (management strategic decision).(management strategic decision).

Acting as project manager for the delivery to TMO I analyzed which Acting as project manager for the delivery to TMO I analyzed which team will develop which requirement in order to meet delivery team will develop which requirement in order to meet delivery commitment. Analysis reached dead end due to vague customer commitment. Analysis reached dead end due to vague customer requirements.requirements.

Clarifications from the customer revealed major gaps from the product Clarifications from the customer revealed major gaps from the product roadmap and from the project scope as was perceived by the division roadmap and from the project scope as was perceived by the division managers.managers.

Project was managed from day 1 under a major risk to delivery dates Project was managed from day 1 under a major risk to delivery dates and contents, risks were surfaced to customer representatives in order and contents, risks were surfaced to customer representatives in order to enable the customer to update TMO relevant campaigns.to enable the customer to update TMO relevant campaigns.

Page 15: Quality Control Proposal

Case study 2:Case study 2: AU buyers and sellers behaviors analysis AU buyers and sellers behaviors analysis

Australia (AU) catalogs were created during 2013 Australia (AU) catalogs were created during 2013 Q1,Q2,Q3.Q1,Q2,Q3.

I was acting as AU project manager for the AU I was acting as AU project manager for the AU structured data deliveries.structured data deliveries.

In order to asses the ROI on the effort I ran analysis on In order to asses the ROI on the effort I ran analysis on users’ behaviors using different parameters.users’ behaviors using different parameters.

Analysis revealed different aspects unknown to us Analysis revealed different aspects unknown to us regarding the AU market hence directing the business regarding the AU market hence directing the business where to go next.where to go next.

Page 16: Quality Control Proposal