Category: agile

Agile – Daily Stand-up ”; Previous Next Daily stand-up, as the name suggests, is a daily status meeting among all the members of an agile team. It not only provides a forum for regular updates but also brings the problems of team members into focus so that it can be quickly addressed. Daily stand-up is a must-do practice, no matter how an agile team is established regardless of its office location. What is Daily Stand-up? A daily stand-up is a daily status meeting among all team members and it is held roughly for 15 minutes. Every member has to answer three important questions − What I did yesterday? What I”ll do today? Any impediment I am facing…/ I am blocked due to… Daily stand-up is for status update, not for any discussion. For discussion, team members should schedule another meeting at a different time. Participants usually stand instead of sitting so that the meeting gets over quickly. Why Stand-up is Important? The benefits of having a daily stand-up in agile are as follows − The team can evaluate the progress on a daily basis and see if they can deliver as per the iteration plan. Each team member informs all about his/ her commitments for the day. It provides visibility to the team on any delay or obstacles. Who Attends a Stand-up? The scrum master, the product owner, and the delivery team should attend the stand-up on a daily basis. Stakeholders and Customers are encouraged to attend the meeting and they can act as an observer, but they are not supposed to participate in stand-ups. It is the scrum master”s responsibility to take note of each team member”s queries and the problems they are facing. Geographically Dispersed Teams Stand-ups can be done in multiple ways, in case the agile team members are operating from different time zones − Select a member on a rotational basis, who can attend the stand-up meeting of teams located in different time zones. Have a separate stand-up per team, update the status of the stand-up in a tool such as Rally, SharePoint, Wikis, etc. Have a wide variety of communication tools ready like conference call, video conferencing, instant messengers, or any other third-party knowledge sharing tools. Print Page Previous Next Advertisements ”;

Agile – Release Planning ”; Previous Next The purpose of release planning is to create a plan to deliver an increment to the product. It is done after every 2 to 3 months. Who is Involved? Scrum Master − The scrum master acts as a facilitator for the agile delivery team. Product Owner − The product owner represents the general view of the product backlog. Agile Team − Agile delivery team provides insights on the technical feasibilities or any dependencies. Stakeholders − Stakeholders like customers, program managers, subject matter experts act as advisers as decisions are made around the release planning. Prerequisites of Planning The prerequisites of release planning are as follows − A ranked product backlog, managed by the Product Owner. Generally five to ten features are taken which the product owner feels that can be included in a release Team”s input about capabilities, known velocity or about any technical challenge High-level vision Market and Business objective Acknowledgement whether new product backlog items are needed Materials Required The list of materials required for release planning is as follows − Posted agenda, purpose Flip charts, whiteboards, markers Projector, way to share computers having data/tools required during planning meeting Planning data Planning Data The list of data required to do release planning is as follows − Previous iterations or release planning results Feedback from various stakeholders on product, market conditions, and deadlines Action plans of previous releases / iterations Features or defects to be considered Velocity from previous releases/ estimates. Organizational and personal calendars Inputs from other teams and subject matter experts to manage any dependencies Output The output of a release planning can be the following − Release plan Commitment Issues, concerns, dependencies, and assumptions which are to be monitored Suggestions to improve future release plannings Agenda The agenda of a release planning can be − Opening ceremony − Welcome message, review purpose and agenda, organizing tools and introduction to business sponsors. Product Vision, Roadmap − Show the large picture of the product. Review previous releases − Discussion on any item which can impact the plan. Release name / theme − Inspect the current status of roadmap themes and do the required adjustments, if any. Velocity − Present the velocity for the current release and of previous releases. Release schedule − Review key milestones and decision on time boxes for release and iterations within release. Issues and concerns − Check any concerns or issue and record them. Review and Update the Definition of Done − Review the definition of done and make appropriate changes based on technology, skill, or changes in team members since the last iteration / release. Stories and items to be considered − Present the user stories and features from the product backlog to be considered for scheduling in the current release. Determine sizing values − If the velocity is unknown, then plan the sizing values to be used in the release planning. Coarse the size of stories − The delivery team determines the appropriate size of the stories under consideration and splits the stories into multiple iterations if a story is too large. The product owner and the subject matter experts clarify the doubts, elaborate the acceptance criteria, and make proper story splits. The scrum master facilitates the collaboration. Map stories to iterations − The delivery team and the product owner move the stories/defects in the iterations based on the size and velocity. The scrum master facilitates the collaboration. New concerns or issues − Check any new issues based on previous experience and record the same. Dependencies and assumptions − Check any dependencies/assumptions planned during the release planning. Commit − The scrum master calls for the planning. Delivery team and Product owner signal it as the best plan and then commit to move to the next level of planning, that is, iteration planning. Communication and logistics planning − Review/Update the communication and logistics planning for the release. Parking lot − Process parking lot means all items should be either resolved or set as action items. Distribute Action items and action plans − Distribute the action items among their owners, process the action plan. Retrospect − Solicit feedback from participants to make the meeting successful. Close − Celebrate the success. Print Page Previous Next Advertisements ”;