The requirements undergo a hard time during the entire process in any agile development project. Requirements are classically written on a “nick of time,” or “just to get the code” basis. This may have several business edges, but this gives rise to making the job of a QA Lead very cumbersome. Even before knowing the project they must start developing the test plans, which must be tailored to satisfy the dynamic requirements. For making the life of a QA lead easy I am going to elaborate some easy ways to achieve writing test plans. Scroll down to the end of...

In this article we will walk you through the Sprint Retrospective Questions (specific to the questions you can ask in retrospective). The questions, given here can have many possible answers. Try to choose the questions relevant to your project and collect response from your entire team individually in a collective manner to understand and implement better in the upcoming Sprints. (more…)

Definition of Done (DoD) – Definition Definition of done is the key to an effectively performing Scrum team. The Definition of Done and user acceptance criteria (functional acceptance) are orthogonal for a feature. It is a complete checklist of value added and essential activities that emphasize the worth of a feature and not the performance of that feature. Definition of done is well-versed by reality where it captures activities that can be committed by the team to be completed at each level (feature, sprint, release). (more…)

Product Manager in Agile Development – By Definition You may be wondering, why a definition about the Product manager is required? As everyone is aware of the same. It looks like I am teasing you with this definition. Trust me the intention is not to tease you but to make you understand that, in what way a “Product Manager” (PM) comes into the frame of Agile development is the most perplexing features while looking at a Scrum method in Agile development. From the textbook standpoint, viewing the whole thing using that lens, it is significant to realize that Scrum was...

Australia and New Zealand Banking Group (ANZ) has declared to implement agile ways adopted by Google and Spotify to swiftly convince the shifting customer mindset. CEO Shayne Elliott, ANZ added, further to satisfy customer needs, this revolution made in its working style will enlighten the staff and improve efficiency. (more…)

Scrum is such as integral part of Agile that these two terms are often used interchangeably even by the IT industry insiders. One of the most rigorously used and abused frameworks of Agile, Scrum is one of those concepts which seem easy at the first sight but come with a tricky implementation. This tricky implementation part has many a times damaged the scrum stand up meetings. The entire purpose of these daily scrum stand up meetings is to give an opportunity to all the team members to share such information with the rest of the team that they must be...

Though nowhere mentioned in the Agile manifesto, the Agile development mechanism has always been regarded as exclusively designed for IT industry. However, in the close to 2 decades of its existence, a number of companies belonging to industries other than IT have gladly adopted Agile development practices and gained immense profits out of it. Presence of APM (Agile Project Management) enablers gives ample opportunities for non-software development companies to adapt APM theory. Companies undertaking project planning and control have been using orthodox management methods with unsatisfactory results for far too long. The companies hence went looking (and are still looking)...