Agile testing involves all members of a cross-functional agile team, with special expertise contributed by testers, to ensure delivering the business value desired by the customers at frequent intervals. Agile is constantly changing, so to help you stay ahead of the curve we have gathered four helpful Agile articles.
Every AGILE team essentially maintains a Wall to display the committed work and progress for a sprint. AGILE task board or the Wall can be a physical wall or a digital one which uses some online tool. A physical task board is very simple to create and is often the choice of new AGILE teams. On the other hand, a digital wall offers sophistication of an online tool and advanced features. Nonetheless, each of the option has it’s own pros and cons.
Physical Wall can be created at minimal cost. A big wall, some sticky notes, pens, an ounce of creativity and you are good to go! As opposed to digital walls, what the team can do and show is not limited by a tool’s capability. You can write, draw, and paste things on a wall! It can be customized to any extent and in tons of ways and can be so much fun! On the contrary, digital walls incur a cost and are not as customizable as their physical counterparts.
There is not a strict rule/criteria for choosing the type of wall. As for everything AGILE, use which works best for your team! Which wall have you used and found useful?
Whether it is pure SCRUM or ScrumBan, it calls for the use of user stories to represent the specifications. A user story is a high-level definition of customer requirement and has to be “just-the-correct” size. It should be sliced small enough to be completed in short time period and large enough to deliver an appreciable amount of work. Estimated based on story points (or relative estimations for mature enough teams) and the progress being tracked down on digital walls/physical walls, user stories help calculate the team’s velocity.
All sounds nice and easy if it is only user stories that move across the wall in swimlanes, but it gets complicated when bugs come into the picture. There are several ways to represent bugs on the AGILE Wall and all of them have pros and cons. Read the article to find out more.
Dror Helper is a senior consultant at CodeValue. His first encounter with agile happened a few years ago while working for a software vendor specializing in unit testing tools, since then he has been evangelizing Agile wherever he went – at his work, speaking at conferences and today as a consultant.
In this video, Helper shares his experience implementing Agile practices in his team, outlining the do and don’ts that can make all the difference. He addresses teams working in a non-agile environment.
Scrum of scrums can be used to scale the daily stand-up meeting when multiple teams are involved. Its purpose is to support agile teams in collaborating and coordinating their work with other teams. Several authors have shared views on scrum of scrums, with experiences of using them.
Charles Bradley wrote a blog post about resurrecting the much-maligned scrum of scrums where he described how the scrum of scrums can help teams who are working together on the same product to (re-)plan and coordinate development work:
“I believe and have experienced that a Development Team-focused approach honors the principles behind Scrum, honors the principles of the Daily Scrum practice at the team level, and results in more value being delivered sooner to customers. In my experience, an effective Scrum of Scrums, for and by the Development Teams, leads to a big boost in the Development Teams’ self-organization skills, impediments being removed quicker, higher quality products, and higher valued products delivered sooner.”