Keeping pace…. Agile way… by smita on 4/25/11
I was very curious when I heard the news that we are going to work in Agile way for coming project. I was very excited and waiting to know more about what is Agile all about. One fine day we had long con call with Agile experts sitting somewhere in UK
and very next day we started working Agile.
Now we are in Agile, everyday scrum call at 11.00 AM. This is stand up call for all of us as scrum team and I as tester should tell only 3 things in this call i.e what I did yesterday, what is my plan for today and blockers I faced that to in just 2 min.Scrum master was present but he didn’t interfered as his job to protect scrum team and try to resolve impediment faced by team members.
Wow, life is easy now; I don’t have to update status everyday in long meetings and no need to waste my time preparing for such meetings.
But Agile is not about all this, it is much more than just attending scrum calls daily.
We all agreed upon certain user stories to get complete in next 2 weeks. So far I dealt with requirements but user stories was all together new term for me.
User stories are business requirements which are not exactly functional requirements
but its our duty to figure out test cases based on user stories.
For this sprint we decided to work on only four stories and the sprint is for 2 weeks.
So we started scripting and came to know that the testing will start in next 4 days,
Again the new term sprint, which will be usually 2 to 4 weeks and both the development and testing should get complete in this period. Surprise!! the estimate is very much different then the usual because we got just two weeks, for development and testing.
We pulled up our socks to complete scripting in time.
Here comes the 1st build, everyone was very much curious the way we complete the very first build.
We started with logging in into visual studio and selecting today’s task.
As test cases were ready and I started with very 1st story. One day has gone and we have been asked to fill up burn down chart for that day.So I need to write the details about how many hours I spent on 1st story! As we agreed upon 4 user stories for this sprint we got 8 days to complete entire testing along with automation??
Oh!! now automation came into picture which I was not considering at all.
So I have to automate all the 4 stories in this sprint.
Now this was real challenge, I have completed all the 4 user stories, filed bugs but when
I will test those bugs? Lower priority bugs got fixed but some major changes went into
Sprint backlog. So this will get added into new sprint now.
We started scripting automation test cases and finally the sprint got over successfully.
Here comes the signoff for this sprint, I sent formal mail saying we are happy to signoff these 4 user stories etc etc.
Hats of to our agility and Agile…..No time to breath, as next sprint is starting from tomorrow :)
I was very curious when I heard the news that we are going to work in Agile way for coming project. I was very excited and waiting to know more about what is Agile all about. One fine day we had long con call with Agile experts sitting somewhere in UK
and very next day we started working Agile.
Now we are in Agile, everyday scrum call at 11.00 AM. This is stand up call for all of us as scrum team and I as tester should tell only 3 things in this call i.e what I did yesterday, what is my plan for today and blockers I faced that to in just 2 min.Scrum master was present but he didn’t interfered as his job to protect scrum team and try to resolve impediment faced by team members.
Wow, life is easy now; I don’t have to update status everyday in long meetings and no need to waste my time preparing for such meetings.
But Agile is not about all this, it is much more than just attending scrum calls daily.
We all agreed upon certain user stories to get complete in next 2 weeks. So far I dealt with requirements but user stories was all together new term for me.
User stories are business requirements which are not exactly functional requirements
but its our duty to figure out test cases based on user stories.
For this sprint we decided to work on only four stories and the sprint is for 2 weeks.
So we started scripting and came to know that the testing will start in next 4 days,
Again the new term sprint, which will be usually 2 to 4 weeks and both the development and testing should get complete in this period. Surprise!! the estimate is very much different then the usual because we got just two weeks, for development and testing.
We pulled up our socks to complete scripting in time.
Here comes the 1st build, everyone was very much curious the way we complete the very first build.
We started with logging in into visual studio and selecting today’s task.
As test cases were ready and I started with very 1st story. One day has gone and we have been asked to fill up burn down chart for that day.So I need to write the details about how many hours I spent on 1st story! As we agreed upon 4 user stories for this sprint we got 8 days to complete entire testing along with automation??
Oh!! now automation came into picture which I was not considering at all.
So I have to automate all the 4 stories in this sprint.
Now this was real challenge, I have completed all the 4 user stories, filed bugs but when
I will test those bugs? Lower priority bugs got fixed but some major changes went into
Sprint backlog. So this will get added into new sprint now.
We started scripting automation test cases and finally the sprint got over successfully.
Here comes the signoff for this sprint, I sent formal mail saying we are happy to signoff these 4 user stories etc etc.
Hats of to our agility and Agile…..No time to breath, as next sprint is starting from tomorrow :)
No comments:
Post a Comment