• Skip to primary navigation
  • Skip to content
  • Skip to footer

Software Quality Services

Software Consultancy & Training Experts focused on empowering Development & IT teams in designing, building and measuring,high quality reliable software

  • Who Are We?
    • Leadership
    • Mission & Values
  • Services
    • Consulting
    • Onsite Training
  • Blog
  • Contact
  • Hire Us
You are here: Home / Services / Software Reliability & Software Quality / Agile Development Process

Agile Development Process

What is Agile Development?

  • A software development methodology that focuses on:
    • Individuals and interactions over processes and tools
    • Working software over comprehensive documentation
    • Responding to change over following the plan
    • Customer Collaboration over contract negotiation
  • Agility is about:
    • Embracing change rather than attempting to resist it
    • Focus on talent and skills of individuals and teams

Agile Development: Xtreme Programming

  • A pair of Engineers collaborating on ALL their development work
  • Involves real-time collaboration with other team member/s
  • Inspections not required
  • ODC (Orthogonal Defect Classification) Metrics Collected/Analyzed

Agile Development: SCRUM

  • A Cross Functional team collaborating on ALL their development, & test work
  • Involves real-time collaboration with other team member/s, including business teams/product management
  • Inspections not required
  • ODC Metrics Collected/Analyzed

Agile Development Essentials

  • Modular Architecture, hence we can break the software into smaller pieces, and TEST each module
  • Automated and repeatable development testing for each module
  • The development tests cover design and interface for each module
  • ODC Metrics Collected/Analyzed for development test

Agile Development Process

  • Automated testing, The main reason for Agile development is to test early and often
  • Find Defects at the earliest point in the lifecycle (Left Shift)
  • For any software change (even one Line of code) in any module, run the full interface and design test automated suite for that module, prior to merging the module (Software Reliability Growth)
  • Apply ODC to the defects to learn trends and weakness for each software module
  • Code Refactoring, due to excessive testing in agile, and excessive defect fixes, Agile code bases need to be redesigned & rewritten, every 5 years or so.
  • Continuous Integration/Delivery, Business realties catch up with the best of us, we have to continually adapt to business and customer input. The continuous Integration plan and cross functional team approach is best suited to adapt with changes from the business & customers
  • Theory of continuous integration – “The less the time between integration’s, the more efficient the integration effort”

Agile Development vs Traditional Development

Agile vs Traditional Development

Other characteristics of Agile Development

  • Just sufficient documentation – enough to develop and understand the product
  • Daily Stand-up meetings – Communication mechanism where everyone literally stands during the meeting
  • Daily Stand-up meetings also discuss Defects classified via ODC
  • Code Inspections not required
  • Phenomenal adaptation to change requests from business and customers

What contributes to Higher Productivity for Agile Development?

  • Finding and Fixing defects at the earliest point in the life cycle, built in Left Shift of development process
  • Automated testing and modular architecture allow for a Software Reliability Growth model to be built in the Agile process
  • Risk mitigation earlier in the life cycle, applying ODC in development test
  • Code Inspections not required, this saves money for high reliability systems
  • Finally, speed, speed, speed, Agile can deliver twice as much functionality with higher quality than traditional development
  • Speed, speed, speed, Agile can deliver twice as much functionality with higher quality than traditional development
  • Finally, Agile is not a way of doing development, but the ONLY WAY TO DO SOFTWARE DEVELOPEMNT

Footer

Services

  • Software Consulting
  • Onsite Training

Featured Post

Zero Defect Initiative for Software

Zero Defect Initiative for Software Development What is a Zero Defect Initiative? The Goal for a Zero Defect Initiative is to target zero known high severity software defects, a maximum of 10 low severity defects, including 3rd Party Vendor defects at the following SDLC phases: Entry in to System Test Customer Field Trials (Beta Test) […]

Find Us On

LinkedIn
Facebook
Google +
Twitter

About Us

We at SW Quality are the foremost experts in Software Quality and Reliability. We have extensive experience in designing and building high reliability systems for IT, SaaS, Industrial Applications, Telecom, Insurance & many other industries. We pride ourselves on offering Left shift initiative where we help our customers identify defects at the earliest point in the software life cycle. Our methodology is based around a proactive quality culture, and we work hard to deliver significant value to each and every one of our clients. Headquartered in Wisconsin, our consultants travel all over the US & the World to empower some of the world's largest organizations to build better software.

Reviews

"Vivek Vasudeva is an expert in Software Development & Quality"

Vivek Vasudeva is a Six Sigma Master Black Belt who is not only is expert in Software Development and Quality - he is passionate about it. He explores new approaches, finds both proven and promising new methods that can minimize defects, model the rates of error generation and removal, and control the software processes to meet both development time and quality goals.

I've been amazed with his enthusiasm as I've seen him drive efforts to develop and use models to improve Software Availability, System Performance, and QoS (Quality of Service) in complex communication systems, and in emerging technologies. Vivek's enthusiasm, intuitive insights and exceptional intelligence, and the rate at which he learns new things, enable him to take on any challenge.


Written by: Eric Maass
Software Development & Quality
Date published: 06/02/2009
5 / 5 stars

© Copyright 2016 Software Six Sigma Experts LLC · All Rights Reserved

  • Terms of Use
  • Privacy Policy
  • Contact