Agile Quality Assurance
The Agile approaches are changing the conversation about software development. Agile shifted our attention to small teams incrementally delivering quality software. The old ideas about testing at the end of the coding phase no longer applicable. We need to think new about the role of Quality Assurance in Agile Projects.
Agile Testing abandons the old notion about how Testers communicate. Requirements and design docs are insufficient, as are test plans and bug reports. Agile Testing sees docs as interesting texts, partly fictional, often useful. Documents are as good as they are going to get. Testers need to join in the conversations with developers and users.
New models for Test Development
Testing may be degraded by poor or late docs, but it should not be blocked entirely.
Testers should use sources of information other than project docs when designing tests.
Test design must take into account what is learned from running tests.
The tester must take explicit, accountable action in response to dropped handoffs, new handoffs and changes to the contents of handoffs.
Source: http://www.mcbreen.ab.ca/
Showing posts with label Agile. Show all posts
Showing posts with label Agile. Show all posts
Sunday, October 25, 2009
Monday, October 5, 2009
Agile 3: Quality Assurance and Agile projects
Quality Assurance and Agile projects
This post is part 3 of an Agile series; my last post was about measuring an Agile progress. In this post I’m talking more about, what are the QA Agile practices we are using in my company? Quality Assurance and Agile projects are very complex combo in any agile project. It’s true QA decrease the speed of any project and if project is on Agile, it certainly create complexity in an Agile methodologies. However being an Agile project that does not mean you can kick out the QA and close project on time with in budget. At the end stakeholder don’t appreciate if deliverable are on time and in budget but quality is shit. That’s the point mostly all project manager miss when they push team to complete project.
Anyway that an other story, but let’s talk about different dimensions in an QA world for an Agile project. I’m not explaining any dimension in this post, because the topic is so horizontal and wide that we can write whole book on it. So just focus on our scope, and they are not unique to QA world.
~ Functional Testing
~ Test Management
~ Independent Testing
~ Performance Testing
~ Security Testing
~ Service-Oriented Architecture (SOA) Testing
~ Transport Testing (SAP)
You can argue with me that there are so many other QA dimensions, which I can add. That’s true, but the thing is “IT Best Practices are not about right or wrong; it’s more about what and how.”
This post is part 3 of an Agile series; my last post was about measuring an Agile progress. In this post I’m talking more about, what are the QA Agile practices we are using in my company? Quality Assurance and Agile projects are very complex combo in any agile project. It’s true QA decrease the speed of any project and if project is on Agile, it certainly create complexity in an Agile methodologies. However being an Agile project that does not mean you can kick out the QA and close project on time with in budget. At the end stakeholder don’t appreciate if deliverable are on time and in budget but quality is shit. That’s the point mostly all project manager miss when they push team to complete project.
Anyway that an other story, but let’s talk about different dimensions in an QA world for an Agile project. I’m not explaining any dimension in this post, because the topic is so horizontal and wide that we can write whole book on it. So just focus on our scope, and they are not unique to QA world.
~ Functional Testing
~ Test Management
~ Independent Testing
~ Performance Testing
~ Security Testing
~ Service-Oriented Architecture (SOA) Testing
~ Transport Testing (SAP)
You can argue with me that there are so many other QA dimensions, which I can add. That’s true, but the thing is “IT Best Practices are not about right or wrong; it’s more about what and how.”
Tuesday, September 29, 2009
Agile - 2 : Evaluating Agile Project Acceptance
Evaluating Agile Project Acceptance
This post is second part of my last post about Agile. This post is about what factores we are using to evaluating how well Agile development works on Agile project is essential in my company. Agile best particle can help project team to recognize potential improvements to how they choose to work. Effective measurement enables team to more effective team. Effective management promotes close collaboration and sharing of best practices among teams.
The Factors we are using in my company to help in measuring Agile acceptance are:
1. Daily Stand up meeting:
2. Time Boxed iteration
3. Working software/ functionality
4. Estimating
5. Prioritized backing
6. Feedback used
These factors are also depends on size of project.
This post is second part of my last post about Agile. This post is about what factores we are using to evaluating how well Agile development works on Agile project is essential in my company. Agile best particle can help project team to recognize potential improvements to how they choose to work. Effective measurement enables team to more effective team. Effective management promotes close collaboration and sharing of best practices among teams.
The Factors we are using in my company to help in measuring Agile acceptance are:
1. Daily Stand up meeting:
2. Time Boxed iteration
3. Working software/ functionality
4. Estimating
5. Prioritized backing
6. Feedback used
These factors are also depends on size of project.
Tuesday, September 8, 2009
Agile
I just wanted to say "Happy Labour Day" to my readers in Canada/ U.S. I hope you are enjoyed a day off. This post is my first post on series of posts on Agile methodology. I don’t want to load my reader with all information at one shot, that’s why I’m breaking Agile methodology into chain of series. I think this methodology is quite new and we have to give some time to this methodology to mature. Furthermore no methodology can’t mature with in it 2-3 years, so Agile methodology also need some more time to mature and IT industries also need more time to alliance with Agile. They also need more time to adjust with this new methodology.
So just for curiosity, I want to know first, what the word Agile means. So according to thefreedictionary.com and link: www.thefreedictionary.com/agile
Def: ag·ile (jl, -l)
adj.
1. Characterized by quickness, lightness, and ease of movement; nimble.
2. Mentally quick or alert: an agile mind.
[French, from Latin agilis, from agere, to drive, do; see ag- in Indo-European roots.]
It’s an adjective with meaning quick in movement, lightness.
Defining Agile in Software development:
An iterative and incremental (evolutionary) approach performed with project stakeholders in a highly collaborative and self organizing manner with just the right amount of ceremony to produce high quality software and timely manner that meets stakeholders changing needs. For more information click on IBM website on agile, link: www.ibm.com/software/rational/agile/resources/
So just for curiosity, I want to know first, what the word Agile means. So according to thefreedictionary.com and link: www.thefreedictionary.com/agile
Def: ag·ile (jl, -l)
adj.
1. Characterized by quickness, lightness, and ease of movement; nimble.
2. Mentally quick or alert: an agile mind.
[French, from Latin agilis, from agere, to drive, do; see ag- in Indo-European roots.]
It’s an adjective with meaning quick in movement, lightness.
Defining Agile in Software development:
An iterative and incremental (evolutionary) approach performed with project stakeholders in a highly collaborative and self organizing manner with just the right amount of ceremony to produce high quality software and timely manner that meets stakeholders changing needs. For more information click on IBM website on agile, link: www.ibm.com/software/rational/agile/resources/
Subscribe to:
Posts (Atom)