Author Topic: Did you follow the agile-Scrum methodology in your project?  (Read 548 times)

1183167903

  • Global Moderator
  • Newbie
  • *****
  • Posts: 12
Did you follow the agile-Scrum methodology in your project?
« on: August 25, 2018, 05:18:49 am »
Did you follow the agile-Scrum methodology in your project?

1183091306

  • Global Moderator
  • Newbie
  • *****
  • Posts: 11
Re: Did you follow the agile-Scrum methodology in your project?
« Reply #1 on: September 22, 2018, 12:57:37 am »
Yes, I have worked on one project which was completely agile-scrum project. The project was to build a web application for a residual (royalties paid to actors, writers, directors) system that was an upgrade from an older legacy system.
What differentiated an agile project from other hybrid or waterfall-methodologies based projects is how the team is coordinated in achieving the tasks important to project completion.
Agile-scrum strictly works with the deliveries in sprints. So, the biggest challenge that the team faces initially is to establish itself into a sprint mode. This requirement forces the team to not only deliver the points taken up for the current sprint, but also maintain consistency with accelerating complexity of the system.
A high level of coordination and understanding is required between the development and business analyst team that results in breaking down epic stories to manageable user stories. A lot of agile-scrum projects are grossly under-estimated in effort and time parameters and hence these are some of the pitfalls that need to be taken care of.
A typical sprint has the first few days dedicated to development followed by testing and then handing over to business analyst team before demonstrating to product owners or business stakeholders.
Each day has a stand-up meeting that requires all the team members to give their update on work done on the previous day, any issues raised, task that they will be working for the day.
A mid sprint meeting for grooming the stories was used in my project. This time was used to groom future stories. The development and testing team effort estimates were determined for the future stories.
At the end of each sprint there was a demonstration followed sprint review. The performance of the team in terms of points taken vs achieved, velocity, burn down charts etc. are showcased.
The team also has a sprint retrospective that focuses on improving any issues found in the sprint that can be fixed for the next sprint to improve the performance.
Although a scrum team is supposed to be a small team with 5-6 people, I have worked in a large team with more than 10 people including the testers.