Ally's a QA

2008-Jan-26 - Making it Agile

Posted in My thinkings

To avoid becoming more and more conservative in releasing our product, the executives ordered that we introduced Agile mentality, and made our software development AGILE!

 

Well, before that, we do not have any clue about what Agile is, neither we have a successful agile pilot team. So we, the development group, started whitehanded.

Does it mean shorter schedule, no documentation, less test...?

 

After a couple of weeks of study and discussion, we found some difficulties in implementing Agile process (maybe it's not called a process for Agile) from our engineers' point of view. And the top 3 are:

 

1. Instant face to face communication among all stakeholders are not possible.

Because we are a transnational company, and the stakehoders, i.e. marketing team, development team, sales, tech writers, decision making managers, etc. are locating through out the world in different time zones.

 

2. Lack of senior, experienced engineers.

All developers and QAs in our team have only 2~5 years software development experiences. And nobody have ever involved in an agile team. 

 

3. Working model is not decided yet a new cycle of product development is on the road.

We have started our new version of product development, but how to work agile is still in discussion.

 

I will follow up what happen on our agile development in my coming blogs.

 


2008-Feb-4 - I've gone through this too...

Posted by michaeljf
and posted some of my experiences on it. We also are a transnational company, but some things that are Agile you can do.

1) Local Groups to have standups, if you are transnational then you are most likely doing Dev and QA in the same space. Try having stand ups and see how it goes, doesn't need to be too formal, just enough to share status and next steps.

2) Make some mini iterations, pick some functional areas and try them as an Agile project, jumping into the pool when you don't know how deep it is does not bode well, try something small first and see if it fits your teams, then adapt it afterwards to see how it works.

3) Information Radiators, this is the piece we took to heart here, in each site there is a PowerPoint information radiator on the project running. Granted, not the best mechanism, but it has project status and its updated every week so people can judge the progress.

Suddenly going Agile, doesn't help you if you don't really understand it, and your environment doesn't fit it. Take some time and read the books and investigate, then adapt what works to your organization. Remember though its not "No Documentation" its "No UNNECESSARY Documentation".
Permanent Link

<- Last Page :: Next Page ->

About Me

Here I share my experiences and thoughts as a QA engineer, and a place to put my notes.

Search This Blog

Categories

My thinkings
My knowledge base
My tools

Links

Home
View my profile
Archives
Friends
Email Me

Friends

whollymindless
strazzerj
syed1982
Nivetha
mferris
ukkuru
michaeljf
agvasqa
priyabala
srini847
spikyone
naba123