| Don Tan 的个人资料Don's space - Software D...日志列表 |  工具  帮助 |
|
11月28日 What's in it for Testers adopting SCRUM agile software developmentWhen I first got introduced to "SCRUM" agile development, I didn't knew what it's all about. All I knew was we have to deliver software faster while meeting/maintaining quality standards once it's delivered. The first project that I worked on adopting "SCRUM" agile development was Micosoft.com's RSS directory (www.microsoft.com/rss). Off course, every person that gets introduced to a new development process/cycle would wonder, Will this work? What are the pros and cons? Is it worth the time and effort? What if we don't deliver in time? OR if we deliver on time what's the quality bar? and so on...
What's SCRUM agile development? There are a lot of resources out there and yet wikipedias definition of "SCRUM" agile development seems to summarize it pretty well. http://en.wikipedia.org/wiki/Scrum_%28development%29
There has been a lot of skepticism around scrum agile development simply because it failed for some folks while other found it to suit their development environment.
Based on experience, most common problems that I've seen encountered for this methodology are:
- Requirements are unclear during the planning phase
- Requirements keep changing during sprints
- Definition of "Done" on stories or feature work (What does this mean for Scrum team members and how is it defined?)
- Tools/Technologies (What tool and technologies would scrum team members conform to?)
These are some of the areas that a Scrum team would identify and mitigate right away while in the early stages of the scrum process.
How does the tester (in this case me
 ) get involved in this development methodology? Well involved. I found myself well engaged on areas such as design, feature, and/or development work. But really as a tester our main focus is Quality Ensurance. By the way, I come to realize when using scrum agile development for our projects, QA is misleading. Do we really want to say Quality "Assurance" or Quality "Ensurance". Assure vs. Ensure. Off the side topic that's outside the scope of this post.How does a tester get started? Understand SCRUM development process and do your research in advance. Don't enter a scrum process if you don't have at least some understanding of its concept. Most important areas: Requirements and clear definition of "Done". Every project is unique in a sense that SCRUM adoption will be different for every project. However the concept applies for all.
I encourage folks to share your experiences and best practices especially to software testers who have been practicing scrum agile development.
- "Do you know the difference between education and experience? Education is when you read the fine print; experience is what you get when you don't." ~Pete Seeger 评论 (2)
引用通告此日志的引用通告 URL 是： http://dtanlive.spaces.live.com/blog/cns!241296DF6BCD364B!115.trak 引用此项的网络日志
|
|
|
