Most Impact Areas - Dimensions

Accuracy, Consistency, and Effectiveness

• Load/Release Building
• Update changed files only
• Commits trigger the building process
• Periodical/Scheduled builds
• Deploy - real time or batch, self or hand over
• MS Make (xml/response file)
• Version the DLL files
• Error Handling - Continue, Skip, or Stop
• Send notification when failed to compile


• Version Control
• Access Control by ID/Branches
• Branching by projects/functionality/bug ticket
• Merging by dev/build
• Repository Management


• Automation
  • Pull code from version control
  • Make/Compile code
  • Package
  • Deploy Code/Data/SQL
  • Notification
  • Advance bug-tracking tickes
  • Routine maintenance/Cleanup
  • Tools/Data Backup


• Integration
  • Bug-Tracking Systems
  • Versioning Control
  • Deployment Verification
  • Automatic QA
  • Code Review
  • Performance Tuning
  • Deploy Code & SQL
  • Central/Single GUI
  • Push information/processes/work out from main stream to supported/integrated environments
  • Pull information from data/status/work order files (xml)


• Optimization
  • Defect/bug-tracking ticke flow
  • Build/Deploy flow
  • Best practice for the company situation
  • Naming convention - Files/Variables
  • Folder Structures


• Audit
• What's in this Build list
• What sliped in this Build list
• Manually handled
• Reports/Dashboards/Scorecards/Excell/Sharepoint/Powerpoint
• Scope/Summary
• Snapshot/Status
• Alert
• RedFlag
  
• Communication
  • Mailing lists for push/deploy/test events
  • Content templates for different groups/roles
  • Feedback
  • 3-way handshaking protocol
  • Realtime sync up (push) all parties by emails, IM, meetings, calls, dashboard, scorecard


• Intelligence
• Trend
• Risk
• Resource Management
• From use cases to knowledge base and peer review feedback


• Backup/Recovery
  • Backup tools periodically
  • Dump/backup repositories periodically
  • Recovery plans/tools for rebuilding the environments in the case of machines/server crashed/moved/upgraded
  • Recovery plans for all manual build in the case of emergency


• Load Test

Issues are found after the push. Panic!?

Few items we can take lessons from this senario:

• Process: What is the standard procedures to follow?
• Manage: Who should take ownership and drive the resolution?
• Resource: Who should involve?
• Documentation: What document is available?
• Lessions: What we learned and how to prevent it in the future?

SQL Code (SP, UDF, TR) Guidelines

• Location
• Coding
• Naming Convention
• Variables

Performance/Load Test Work List

Challenge:
Load test is a cross function activity even we tend to make it a routine work. Because the Keynote account is maintain by the operation team, test users are controlled by DBA, and profiler capture is executed from the hosting company.

Build Status Audit Dashboard

Challenge:
It is pretty common for QA manager, Project managers, and any upper managements to know the status of the next Build. So they can follow up on the progress, analyze the risk, and communicate to the clients accordingly. However, the scope of the build is dynamic. Not only those defect ticket's status are changing all the time along with the progress in multiple departments, the code and tickets might be pulled and included in the last minutes of everyday.

Load/Performance Test in QA before each Build

7 highly effective habits

Dependence to Independence
Habit 1: Be Proactive: Principles of Personal Choice
Habit 2: Begin with the End in Mind: Principles of Personal Vision
Habit 3: Put First Things First: Principles of Integrity & Execution

Independence to Interdependence
Habit 4: Think Win/Win: Principles of Mutual Benefit
Habit 5: Seek First to Understand, Then to be Understood: Principles of Mutual Understanding
Habit 6: Synergize: Principles of Creative Cooperation

Continual Improvement
Habit 7: Sharpen the Saw: Principles of Balanced Self-Renewal