![]() The Complete Guide for Software Developers and Testers — Software Testing Help. Introduction: This is the guide for software developers and testers to understand and start working on the very famous Agile SCRUM methodology for software development and testing. Learn the basic but important terminologies used in Agile Scrum process along with a real example of the complete process. SCRUM is a process in agile methodology which is a combination of Iterative model and incremental model. One of the major handicaps of the traditional water- fall model was that – until the first phase is complete, the application does not move to the other phase. And if by chance there are some changes in the later stage of the cycle, it becomes very challenging to implement those changes, as it would involve revisiting the earlier phases and redoing the changes. Some of the key characteristics of SCRUM include: Self- organized and focused team. History. Scrum is an iterative and incremental agile software development framework for managing product development. It defines "a flexible, holistic product. ![]() No huge requirement documents, rather have very precise and to the point stories. Cross functional team works together as a single unit. Close communication with the user representative to understand the features. Has definite time line of max 1 month. Instead of doing the entire “thing” at a time, Scrum does a little of everything at a given interval. Resources capability and availability are considered before committing any thing. To understand this methodology well, it’s important to understand the key terminologies in SCRUM. Also read => How to Deliver High Value Software Features in a Short Time Period using Agile Scrum Process. Important SCRUM Terminologies: 1. Scrum Team. Scrum team is a team comprising of 7 with + or – two members. These members are a mixture of competencies and comprise of developers, testers, data base people, support people etc. All these members work together in close collaboration for a recursive and definite interval, to develop and implement the said features. SCRUM team sitting arrangement plays a very important role in their interaction, they never sit in cubicles or cabins; but a huge table. Sprint. Sprint is a predefined interval or the time frame in which the work has to be completed and make it ready for review or ready for production deployment. This time box usually lies between 2 weeks to 1 month. In our day to day life when we say that we follow 1- month Sprint cycle, it simply means that we work for one month on the tasks and make it ready for review by the end of that month. Product Owner. The product owner is the key stakeholder or the lead user of the application to be developed. The product owner is the person who represents the customer side. He/she have the final authority and should always be available for the team. He/she should be reachable in case any one has any doubts that need clarification. It is important for the product owner to understand and not to assign any new requirement in the middle of the sprint or when the sprint has already started. Scrum Master. Scrum Master is the facilitator of the scrum team. He/she make sure that the scrum team is productive and progressive. In case of any impediments, scrum master follows up and resolves them for the team. SCRUM Master is the mediator between the PO and the team. He / She keeps the PO informed about the progress of the Sprint. If there are any roadblocks or concerns for the team, discuss with the PO and get them resolved. Like team’s Daily Standup, a standup of the SCRUM Master with the PO happens every day. Recommended read => How To Be a Good Team Mentor, Coach and a True Team- Defender in an Agile Testing World? Business Analyst (BA)A BA plays a very important role in SCRUM. This person is responsible for getting the requirement finalized and drafted in the requirement docs (based on which the user stories are created). If there are any ambiguities in User Stories / Acceptance criteria, he/she is the one approached by the technical (SCRUM) team who then takes it up to the PO else if possible resolves on his own. In large scale projects there may be more than 1 BA but in small scale projects, the SCRUM Master may be acting as the BA as well. It is a good practice to have a BA when a project kick starts. User Story. User stories are nothing but the requirements or feature which has to be implemented. In scrum, we don’t have those huge requirements documents, rather the requirements are defined in a single paragraph, typically having the format as: As a < User / type of user> I want to < Some achievable goal / target> To achieve < some result or reason of doing the thing> For example: As an Admin I want to have a password lock in case user enters incorrect password for consecutive 3 times to restrict unauthorized access. There are some characteristics of user stories which should be adhered. The user stories should be short, realistic, could be estimated, complete, negotiable and testable. A user story is never altered or changed in the middle of the Sprint. It is the responsibility of the SCRUM Master and the BA (if applicable) to make sure that the PO has drafted the User Stories correct with the proper set of the Acceptance Criteria”. If any changes which will impact the sprint release are to be made, then such stories are pulled out of the sprint or they are done as per the hours available. Every user story has an acceptance criterion which should be well defined and understood by the team. Acceptance criteria details down the user story provides the supported documents. It helps to further refine the user story. Anybody from the team can write down the acceptance criteria. Testing team base their test cases/conditions on these acceptance criteria. Epics. Epics are equivocal user stories or we can say these are the user stories which are not defined and are kept for future sprints. Just try to relate it with life, imagine you are going for a vacation. Since you are going next week, you have everything in place like your hotel bookings, sightseeing, travelers check etc. But what about your vacation plan for next year? You have only a vague idea that you may go to XYZ place, but you have no detailed plan. An Epic is just like you next year’s vacation plan, where you just know that you may want to go, but where, when, with whom, all these details you have no idea at this point of time. Baixar Viagem 2 A Ilha Misteriosa 1080P Vs 4K . In a similar way, there are features which required to be implemented in future whose details are not yet known. Mostly feature begins with an Epic and then broken down to stories which could be implemented. Product Backlog. Product backlog is a kind of bucket or source where all the user stories are kept. This is maintained by the Product owner. Product backlog can be imagined as a wish list of the product owner who prioritizes it as per business needs. During planning meeting (see next section), one user story is taken from the product backlog, the team does the brainstorming, understands it and refine it and collectively decides which user stories to take, with the intervention of the product owner. Sprint Backlog. Based on the priority, user stories are taken from the Product Backlog one at a time. The Scrum team brainstorms on it determines the feasibility and decides on the stories to work on a particular sprint. The collective list of all the user stories which the scrum team works on a particular sprint is called s Sprint backlog. Story Points: Story points are quantitative indication of the complexity of a user story. Based on the story point, estimation and efforts for a story are determined. A story point is relative and is not absolute. To make sure that our estimate and efforts are correct, it’s important to check that the user stories are not big. Precise and smaller is the user story, accurate will be the estimation. Each and every user story is assigned a story point based on the Fibonacci series (1, 2, 3, 5, 8, 1. Higher is the number, complex is the story. To be precise. If you give 1 / 2 / 3 story point it means the story is small and of low complexity. If you give points as 5 / 8, it is a medium complex and. Here complexity consists of both development plus testing effort. To decide a story point, brainstorming happens with in the scrum team and the team collectively decides a story point. It may happen that development team gives a story point of 3 to a particular story, because for them it may be 3 lines of code change, but testing team gives 8 story point because they feel this code change will affect larger modules so testing effort would be larger.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |