Posted by SCRUMstudy® on August 12, 2024
Categories: Agile Continuous Integration Iterative Development Product Development
Agile Adaptability Tools are instrumental in facilitating flexibility and responsiveness within Agile frameworks. These tools serve as mechanisms to navigate the dynamic landscape of project development, enabling teams to swiftly adjust to changing requirements and market conditions. Key tools include adaptive planning techniques, such as Agile estimation and release planning, which allow teams to continuously refine and reprioritize tasks based on emerging insights. Additionally, iterative development practices, exemplified by frequent reviews and retrospectives, foster a culture of continuous improvement and adaptation. Collaboration tools like Kanban boards and daily stand-up meetings promote transparency and enhance communication, ensuring alignment across team members and stakeholders. By leveraging these Agile Adaptability Tools, organizations can effectively navigate uncertainty, maximize opportunities, and deliver value to customers in a rapidly evolving marketplace.
Agile Master Practices encapsulate principles and methodologies essential for effective Agile project management. These practices encompass a dynamic approach to project execution, emphasizing collaboration, adaptability, and continuous improvement. Key practices include fostering open communication within cross-functional teams, promoting iterative development cycles, and embracing change as a catalyst for innovation. Additionally, Agile Master Practices advocate for transparent decision-making processes, empowering teams to self-organize and take ownership of project outcomes.
Scrum agile practices encompass a set of principles and methodologies aimed at promoting flexibility, collaboration, and continuous improvement within project management. Key practices include iterative development cycles known as sprints, typically lasting two to four weeks, during which teams deliver incremental pieces of working software.
Project Management Institute’s “PMI Agile Certified Practitioner Exam Content Outline” organizes the tasks practitioners do when working in Agile environment into six domains. Their exam does not test specifically on the domains, so learning their grouping of tools and techniques and knowledge and skills will not be directly applicable to the language of the test. However, this organizational way of looking at Agile tools and tasks has been done to help practitioners learn and understand Agile better.
The six domains of Agile are:
Let’s discuss each domain in more detail.
Value-driven delivery
Creating value is at the core of any project, and Agile methods are designed with the core objective of delivering value on a knowledge worker project. While maximizing value, Agile also has tools and techniques to minimize risks that can erode value. Agile methods also place importance on the customer’s priorities and is designed to deliver elements that have the highest value to the customer first.
Assessing value –.
Planning value – We create a charter detailing the scope, objective, and other attributes of the project. We then use tools such as customer-valued prioritization, relative prioritization, and risk adjusted backlog while preparing the priority list. Which planning value, we also assess the contracting costs of the project.
Delivering value – After planning how we are going to deliver value, we focus on eliminating all activities that do not add value. We can use task and Kanban boards to schedule the backlog. Limiting the Work in Progress (WIP) reduces the potential for reworking and keeps the project going smoothly.
Confirming value – We have executed tasks and created value but is this what the customer wanted? We have to confirm the value we are delivering to know this. We demonstrate prototypes, simulate functionalities to help the customer test the product and see how they work.
Tracking and reporting value – It is not enough that we just deliver value. It is important that we regularly track the rate of delivery of value so that it can be communicated to business stakeholders. Cumulative flow diagrams and burn down graphs are an easy and informative way through which we can assess the development of the project.
Stakeholder engagement
Stakeholders in a project can be anybody who can negatively or positively impact a project. They can be business representatives, customers, the project manager, the development team, or external vendors contributing directly or indirectly to the project. Stakeholder engagement becomes important, because software development involves creating intangible products and the team must have a precise understanding of customer requirements.
Agile projects are subject to constant change which makes it essential that a clear and steady channel of communication is established. All stakeholders must be involved in the project to ensure that it stays on the right track. Teams can use tools such as wireframes, user stories, a user story backlog, and personas to verify their understanding of customer requirements.
Face-to-face communication is the most preferred method of communication on agile projects. They provide the maximum amount of information in the least amount of time. Information radiators such as burn down charts, cumulative flow diagrams, and velocity tracking charts allow us to determine progress of the project, which can be communicated to all the stakeholders.
Soft skills play an important role while engaging with stakeholders. Soft skills such as negotiating and active listening are necessary while dealing with customers. It is also essential that we be familiar with implementing soft skills such as facilitation methods, participatory decision models, and conflict resolution that are primarily concerned with managing teams.
When we talk of managing teams, our leadership skills play a crucial role. Servant leadership is an extremely effective way of leading teams. A servant leader encourages the team to excel by removing any obstacles, motivate and reward the team’s performance.
Boosting team performance
The third domain in Agile deals with boosting team performance practices. In software development, “people factors” incur the highest cost. Therefore, it is extremely important that we obtain the highest return on performance.
The process of forming a team is one of the determinants of success on a project. Building a team goes through the stages of forming (identifying potential team members and bringing them together), storming (the team collaborates and comes up with ideas), norming (teams form rules and normalize their working patterns), and performing (the team works together). During each of these phases, it is important for a leader to know when to play a supporting or directing role. For example, during the storming phase, conflicts can be frequent and the leader will have to step in to help the team members develop methodologies to resolve them.
To get the best out of a team, it should be self-organizing and self-directing. Allowing teams to be self-organizing and self-directing enables team members to manage complex tasks by themselves and figure out the best way to complete the tasks. This capitalizes on the team’s combined expertise and talent.
There are several activities that can help a team boost their performance on Agile projects. Daily stand-up meetings are a quick way to communicate the team’s performance status and identify present and potential issues. To overcome issues and improve continuously, teams might need to be mentored at different stages. During events such as iteration planning meetings or retrospectives, teams might need to be coached at a group level and mentoring can be provided for individual team members when the iteration is underway.
Brainstorming sessions can be used by teams to resolve issues, improve, and innovate processes. Because face-to-face communication is the ideal way to communicate on Agile projects, it is important that the team be located in a common area with space for whiteboards and other information radiators.
Adaptive Planning
Because extensive planning before the project is undertaken can be cumbersome and often does not add any real value, Agile calls for an adaptive approach to planning. Adaptive planning involves creating a basic plan and updating it as the project gets underway. Adaptive planning requires practitioners to maintain close collaboration with the customer to understand his or her requirements more accurately. Collaborative games such as remember the future, prune the product tree, buy a feature, and bang-for-the-buck can be used to help the development team understand customer requirements better.
To make timely deliveries, team members should calculate their estimates as accurately as possible factoring in all diversions and constraints. Wideband Delphi and Ideal Time are some of the techniques which can help teams arrive at an accurate estimate. While estimating the cost of the project, the figures should be presented in ranges as they seem more credible than pin-point figures that can have an air of false confidence.
Iteration and release planning is a vital part of adaptive planning. Releases are bundles of functionality that can be delivered to a customer. While planning a release, the Product Owner/manager, development team, and Agile Expert can use a velocity chart to determine how many features can be completed by the team in a given time. While planning iterations, it important to have a fixed priority list at the beginning of the planning session. Team members have the final say on how much work can be completed, while the product owner gets the final say on the priority of the items included for the iteration. Availability of team members needs to be factored in while planning iterations.
Problem Detection and Resolution
A common saying is, “A stitch in time saves nine,” and this couldn’t be more apt to explain how Agile methods deal with problems. If ignored, problems can have a devastating effect on the project as they not only increase the burden of rework; they make the team fall behind in its plans. It is a double whammy for the team when this happens as it takes twice the resources. Agile practices aids in detecting problems as early as possible and fixing them while they are still small.
Detecting problems is the first step to resolving them. Daily stand-up meetings are an excellent way to identify any issues that team members are facing. Teams can also track issues by calculating cycle times for tasks. If the cycle time is too high, it might indicate a potential problem or that the team has undertaken more work than it can complete. Limiting work in progress can help monitor the project timeline better and track problems more easily. Despite our best efforts, some defects may make their way through to the final product. Escaped defects are the most expensive to fix. Teams can track escaped defects on a graph to analyze trends. This can help refine quality control processes.
Alistair Cockburn describes “failure modes and alternatives,” that are related to the human aspect of performance. Cockburn says that people fail because they can be inconsistent at following a technique, are creatures of habit and prefer to invent new ways than modify existing reliable methods. To counter “failure modes” Cockburn advises that teams should inculcate discipline, receive feedback regularly, and assign work based on personalities of individual team members.
Resolving issues that are identified is the next step. Continuous integration of new code, as and when it is developed, in a repository can help overcome the issues that we find with integration. Validating progress at frequent intervals and at different levels can help us be confident that our work is error-free.
In software development, commonly used techniques are Test-Driven Development (TDD) and Acceptance Test-Driven Development (ATDD). These methods primarily involve writing the tests before any code is written. The codes are written until they pass the tests. Codes might then be “refactored” if necessary, which involves refining the design without altering its behavior.
Continuous Improvement
New insights and learning gained on a traditional project is typically gathered at the end of the project cycle. These insights might not be of much help on the next project unless the two are very similar. That learning could have had more value, if it had been used on the project in which it was learned. Agile methodology seeks to continuously improve throughout the project and encourage applying lessons to the development process as and when we learn it. Retrospectives at the end of each iteration makes the lessons learned available for the very next iteration.
A retrospective typically lasts for about two hours during which time the team gathers data about the different challenges that it faced and the various lessons learned while solving them. The learning is analyzed to see if there exists underlying patterns or any insights. Armed with these patterns and insights, the team plans the next iteration.
As part of continuous improvement, team members should be encouraged to share knowledge they acquire, with other team members. One of the reasons colocation is stressed in Agile projects is because it provides a platform for knowledge sharing through face-to-face communication. To encourage knowledge sharing, team velocity can be tracked at a team level rather than measuring it at an individual level, so that team members are motivated to help each other.
We might be required to tailor agile practices to suit our needs; however, one must careful while doing so. Agile practices have been crafted into a delicate web of interdependent practices and disturbing one can affect other practices. We should be adept at using agile practices before we make any modifications. It might be tempting at times to blame the tools if our work is not going accordingly when the real problem lies in us. We should carefully examine our motives to change practices before we make any alterations.
Posted by SCRUMstudy® on August 12, 2024
Categories: Agile Frameworks SBOK® Guide Scrum Scrum Guide Scrum Principles
Agile Principles form the foundation of Agile methodologies, emphasizing flexibility, collaboration, and customer-centric development. Key principles include prioritizing customer satisfaction through early and continuous delivery of valuable software, welcoming changing requirements even late in development, and delivering working software frequently. Agile encourages close, daily cooperation between business stakeholders and developers, building projects around motivated individuals, and promoting sustainable development. The principles also highlight the importance of simplicity, self-organizing teams, and regular reflection on how to become more effective, fostering an environment of continuous improvement and responsiveness to change.
Scrum principles are the foundation on which the Scrum framework is based. The principles of Scrum can be applied to any type of project or organization, and they must be adhered to in order to ensure appropriate application of Scrum.
The aspects and processes of Scrum can be modified to meet the requirements of the project, or the organization using it, but Scrum principles are non-negotiable and must be applied as described in the framework presented in A Guide to the Scrum Body of Knowledge (SBOK® Guide). Keeping the principles intact and using them appropriately instills confidence to the user of the Scrum framework with regard to attaining the objectives of the project.
Scrum principles are the core guidelines for applying the Scrum framework and should mandatorily be used in all Scrum projects. The Scrum aspects and processes, however, can be modified to meet the requirements of the project or the organization on a project to project basis by the Scrum Core Team.
Posted by SCRUMstudy® on August 09, 2024
Categories: Agile Frameworks Scrum Scrum Master Scrum Principles Scrum Processes
Agile Leadership Principles encapsulate the core values and beliefs that guide effective leadership in agile environments. Central to these principles is fostering a collaborative and empowered team culture, where leaders prioritize individuals and interactions over processes and tools. Agile leaders emphasize delivering working products frequently, responding to change over following a plan, and maintaining close collaboration with customers to ensure their evolving needs are met.
The Agile Leadership Framework is a comprehensive approach designed to empower leaders in Agile organizations. At its core, this framework emphasizes the importance of fostering a culture of collaboration, adaptability, and continuous improvement. Agile leaders are tasked with guiding their teams through uncertainty and complexity while promoting transparency, trust, and accountability. By embracing Agile values and principles, leaders can inspire their teams to innovate, respond to change, and deliver value to customers more effectively. This framework equips leaders with the tools and techniques needed to navigate the dynamic nature of Agile environments, enabling them to drive organizational success in today's fast-paced and ever-evolving business landscape.
Leaders employ listening, empathy, commitment, and insight while sharing power and authority with team members. Supporting leaders are stewards who achieve results by focusing on the needs of the team. This style is the embodiment of the Scrum Master role.
The preferred leadership style for Scrum projects is Supporting Leadership. Larry Spears identifies ten traits that every effective leader should possess:
Scrum believes that all leaders of Scrum projects (including the Scrum Master and Product Owner) should be supporting-leaders who have the above traits.
For more informative articles on Scrum and Agile, please visit www.scrumstudy.com
Follow us on twitter – @SCRUMstudy_
Posted by SCRUMstudy® on August 02, 2024
Categories: Agile Continuous Integration Iterative Development Product Development
Agile Adaptability Tools are instrumental in facilitating flexibility and responsiveness within Agile frameworks. These tools serve as mechanisms to navigate the dynamic landscape of project development, enabling teams to swiftly adjust to changing requirements and market conditions. Key tools include adaptive planning techniques, such as Agile estimation and release planning, which allow teams to continuously refine and reprioritize tasks based on emerging insights. Additionally, iterative development practices, exemplified by frequent reviews and retrospectives, foster a culture of continuous improvement and adaptation. Collaboration tools like Kanban boards and daily stand-up meetings promote transparency and enhance communication, ensuring alignment across team members and stakeholders. By leveraging these Agile Adaptability Tools, organizations can effectively navigate uncertainty, maximize opportunities, and deliver value to customers in a rapidly evolving marketplace.
Agile Master Practices encapsulate principles and methodologies essential for effective Agile project management. These practices encompass a dynamic approach to project execution, emphasizing collaboration, adaptability, and continuous improvement. Key practices include fostering open communication within cross-functional teams, promoting iterative development cycles, and embracing change as a catalyst for innovation. Additionally, Agile Master Practices advocate for transparent decision-making processes, empowering teams to self-organize and take ownership of project outcomes.
Scrum agile practices encompass a set of principles and methodologies aimed at promoting flexibility, collaboration, and continuous improvement within project management. Key practices include iterative development cycles known as sprints, typically lasting two to four weeks, during which teams deliver incremental pieces of working software.
Project Management Institute’s “PMI Agile Certified Practitioner Exam Content Outline” organizes the tasks practitioners do when working in Agile environment into six domains. Their exam does not test specifically on the domains, so learning their grouping of tools and techniques and knowledge and skills will not be directly applicable to the language of the test. However, this organizational way of looking at Agile tools and tasks has been done to help practitioners learn and understand Agile better.
The six domains of Agile are:
Let’s discuss each domain in more detail.
Value-driven delivery
Creating value is at the core of any project, and Agile methods are designed with the core objective of delivering value on a knowledge worker project. While maximizing value, Agile also has tools and techniques to minimize risks that can erode value. Agile methods also place importance on the customer’s priorities and is designed to deliver elements that have the highest value to the customer first.
Assessing value –.
Planning value – We create a charter detailing the scope, objective, and other attributes of the project. We then use tools such as customer-valued prioritization, relative prioritization, and risk adjusted backlog while preparing the priority list. Which planning value, we also assess the contracting costs of the project.
Delivering value – After planning how we are going to deliver value, we focus on eliminating all activities that do not add value. We can use task and Kanban boards to schedule the backlog. Limiting the Work in Progress (WIP) reduces the potential for reworking and keeps the project going smoothly.
Confirming value – We have executed tasks and created value but is this what the customer wanted? We have to confirm the value we are delivering to know this. We demonstrate prototypes, simulate functionalities to help the customer test the product and see how they work.
Tracking and reporting value – It is not enough that we just deliver value. It is important that we regularly track the rate of delivery of value so that it can be communicated to business stakeholders. Cumulative flow diagrams and burn down graphs are an easy and informative way through which we can assess the development of the project.
Stakeholder engagement
Stakeholders in a project can be anybody who can negatively or positively impact a project. They can be business representatives, customers, the project manager, the development team, or external vendors contributing directly or indirectly to the project. Stakeholder engagement becomes important, because software development involves creating intangible products and the team must have a precise understanding of customer requirements.
Agile projects are subject to constant change which makes it essential that a clear and steady channel of communication is established. All stakeholders must be involved in the project to ensure that it stays on the right track. Teams can use tools such as wireframes, user stories, a user story backlog, and personas to verify their understanding of customer requirements.
Face-to-face communication is the most preferred method of communication on agile projects. They provide the maximum amount of information in the least amount of time. Information radiators such as burn down charts, cumulative flow diagrams, and velocity tracking charts allow us to determine progress of the project, which can be communicated to all the stakeholders.
Soft skills play an important role while engaging with stakeholders. Soft skills such as negotiating and active listening are necessary while dealing with customers. It is also essential that we be familiar with implementing soft skills such as facilitation methods, participatory decision models, and conflict resolution that are primarily concerned with managing teams.
When we talk of managing teams, our leadership skills play a crucial role. Servant leadership is an extremely effective way of leading teams. A servant leader encourages the team to excel by removing any obstacles, motivate and reward the team’s performance.
Boosting team performance
The third domain in Agile deals with boosting team performance practices. In software development, “people factors” incur the highest cost. Therefore, it is extremely important that we obtain the highest return on performance.
The process of forming a team is one of the determinants of success on a project. Building a team goes through the stages of forming (identifying potential team members and bringing them together), storming (the team collaborates and comes up with ideas), norming (teams form rules and normalize their working patterns), and performing (the team works together). During each of these phases, it is important for a leader to know when to play a supporting or directing role. For example, during the storming phase, conflicts can be frequent and the leader will have to step in to help the team members develop methodologies to resolve them.
To get the best out of a team, it should be self-organizing and self-directing. Allowing teams to be self-organizing and self-directing enables team members to manage complex tasks by themselves and figure out the best way to complete the tasks. This capitalizes on the team’s combined expertise and talent.
There are several activities that can help a team boost their performance on Agile projects. Daily stand-up meetings are a quick way to communicate the team’s performance status and identify present and potential issues. To overcome issues and improve continuously, teams might need to be mentored at different stages. During events such as iteration planning meetings or retrospectives, teams might need to be coached at a group level and mentoring can be provided for individual team members when the iteration is underway.
Brainstorming sessions can be used by teams to resolve issues, improve, and innovate processes. Because face-to-face communication is the ideal way to communicate on Agile projects, it is important that the team be located in a common area with space for whiteboards and other information radiators.
Adaptive Planning
Because extensive planning before the project is undertaken can be cumbersome and often does not add any real value, Agile calls for an adaptive approach to planning. Adaptive planning involves creating a basic plan and updating it as the project gets underway. Adaptive planning requires practitioners to maintain close collaboration with the customer to understand his or her requirements more accurately. Collaborative games such as remember the future, prune the product tree, buy a feature, and bang-for-the-buck can be used to help the development team understand customer requirements better.
To make timely deliveries, team members should calculate their estimates as accurately as possible factoring in all diversions and constraints. Wideband Delphi and Ideal Time are some of the techniques which can help teams arrive at an accurate estimate. While estimating the cost of the project, the figures should be presented in ranges as they seem more credible than pin-point figures that can have an air of false confidence.
Iteration and release planning is a vital part of adaptive planning. Releases are bundles of functionality that can be delivered to a customer. While planning a release, the Product Owner/manager, development team, and Agile Expert can use a velocity chart to determine how many features can be completed by the team in a given time. While planning iterations, it important to have a fixed priority list at the beginning of the planning session. Team members have the final say on how much work can be completed, while the product owner gets the final say on the priority of the items included for the iteration. Availability of team members needs to be factored in while planning iterations.
Problem Detection and Resolution
A common saying is, “A stitch in time saves nine,” and this couldn’t be more apt to explain how Agile methods deal with problems. If ignored, problems can have a devastating effect on the project as they not only increase the burden of rework; they make the team fall behind in its plans. It is a double whammy for the team when this happens as it takes twice the resources. Agile practices aids in detecting problems as early as possible and fixing them while they are still small.
Detecting problems is the first step to resolving them. Daily stand-up meetings are an excellent way to identify any issues that team members are facing. Teams can also track issues by calculating cycle times for tasks. If the cycle time is too high, it might indicate a potential problem or that the team has undertaken more work than it can complete. Limiting work in progress can help monitor the project timeline better and track problems more easily. Despite our best efforts, some defects may make their way through to the final product. Escaped defects are the most expensive to fix. Teams can track escaped defects on a graph to analyze trends. This can help refine quality control processes.
Alistair Cockburn describes “failure modes and alternatives,” that are related to the human aspect of performance. Cockburn says that people fail because they can be inconsistent at following a technique, are creatures of habit and prefer to invent new ways than modify existing reliable methods. To counter “failure modes” Cockburn advises that teams should inculcate discipline, receive feedback regularly, and assign work based on personalities of individual team members.
Resolving issues that are identified is the next step. Continuous integration of new code, as and when it is developed, in a repository can help overcome the issues that we find with integration. Validating progress at frequent intervals and at different levels can help us be confident that our work is error-free.
In software development, commonly used techniques are Test-Driven Development (TDD) and Acceptance Test-Driven Development (ATDD). These methods primarily involve writing the tests before any code is written. The codes are written until they pass the tests. Codes might then be “refactored” if necessary, which involves refining the design without altering its behavior.
Continuous Improvement
New insights and learning gained on a traditional project is typically gathered at the end of the project cycle. These insights might not be of much help on the next project unless the two are very similar. That learning could have had more value, if it had been used on the project in which it was learned. Agile methodology seeks to continuously improve throughout the project and encourage applying lessons to the development process as and when we learn it. Retrospectives at the end of each iteration makes the lessons learned available for the very next iteration.
A retrospective typically lasts for about two hours during which time the team gathers data about the different challenges that it faced and the various lessons learned while solving them. The learning is analyzed to see if there exists underlying patterns or any insights. Armed with these patterns and insights, the team plans the next iteration.
As part of continuous improvement, team members should be encouraged to share knowledge they acquire, with other team members. One of the reasons colocation is stressed in Agile projects is because it provides a platform for knowledge sharing through face-to-face communication. To encourage knowledge sharing, team velocity can be tracked at a team level rather than measuring it at an individual level, so that team members are motivated to help each other.
We might be required to tailor agile practices to suit our needs; however, one must careful while doing so. Agile practices have been crafted into a delicate web of interdependent practices and disturbing one can affect other practices. We should be adept at using agile practices before we make any modifications. It might be tempting at times to blame the tools if our work is not going accordingly when the real problem lies in us. We should carefully examine our motives to change practices before we make any alterations.
Posted by SCRUMstudy® on July 31, 2024
Categories: Agile Certification Scrum Training
Obtaining a Scrum Master certification equips professionals with the skills and knowledge needed to enhance project adaptability. This certification emphasizes the importance of Agile principles, which prioritize flexibility, continuous improvement, and rapid response to change. As a Scrum Master Certified, individuals are trained to foster a culture of adaptability within their teams, enabling them to pivot quickly in response to evolving project requirements and market conditions. This ability to adapt not only ensures the timely and efficient delivery of project outcomes but also enhances the overall resilience and competitiveness of the organization.
The Scrum Master Certification (SMC™) is designed to equip individuals with the expertise needed to manage and lead Scrum practices effectively. This certification differentiates itself by focusing on the skills necessary for overseeing Scrum teams and ensuring the successful implementation of Scrum principles within a project. Unlike other certifications, which might concentrate on broader project management methodologies, the SMC™ emphasizes practical, hands-on skills specific to the Scrum framework. This hands-on approach includes techniques for effective sprint planning, backlog management, and team collaboration, ensuring that certified Scrum Masters can drive their teams towards successful and efficient project outcomes.
Responsibilities of a Scrum Master
Based on the principles outlined in the SBOK™ Guide, the SMC™ certification emphasizes the importance of:
Posted by SCRUMstudy® on July 25, 2024
Categories: Scrum
Scrum is an agile project management framework primarily used for software development. It emphasizes iterative progress, collaboration, and adaptability to changing requirements. The methodology is structured around fixed-length iterations, known as sprints, which typically last between two to four weeks.
Scrum framework is being used as a successful Project Management or Product Management process in many organizations. It’s been gaining in popularity over the last 15 years, as more and more organizations realize the benefits of Scrum. But before a particular team/organization embraces Scrum or any other Agile process, the biggest hindrance comes from the management, which is generally resistant to change, even in the face of evidence. Let’s look at some of the cultural challenges and how to overcome them:
Independent Decision Making: Scrum encourages independent thinking and decision making, while in most corporate structure, a top-down process of decision making takes places. Also, larger the organization more will be the hierarchies, and independent decision making becomes that much more difficult. To overcome this problem, senior management buy-in is a must, and they have to be convinced of the benefits of religiously following Scrum as a practice.
Customer Relationship: Generally, a traditional vendor-supplier relationship between the organization and the client will not augur well for practicing Scrum. Customers have to get much more involved with the development team, and periodic feedback becomes the norm rather than exception. Here again, the client can appreciate the effort being put in by the development team, if they are closely involved in the planning the backlog and sprint items.
Quality Philosophy: In a traditional structure, quality teams focus a lot on metrics and charts and graphs etc., while Scrum lays emphasis on Collaborative Approach. What it means is that e.g. Testing is not done only by a Tester, but also by a Business Analyst or Technical Manager. Every member of the Scrum team takes the responsibility of bringing in Quality in the development process, and every member contributes to Quality and Process Improvement. Basically, this change of approach means delegating authority, which may face stiff resistance from QA and Testing managers.
Sustainable Pace of Development: In the traditional process, testing and bug fixing happens during the last few weeks of the project phase, wherein everyone from the developers to the technical architects to the testers work overtime and during weekends to complete the task. Agile on the other hand is all about sustainable pace of development, wherein every sprint, the code will be developed and tested. Although this process reduces uncertainty and hastiness, the fact that testers are not used to work in this kind of environment, and their acceptance will take time. To counter this issue, during the first few Scrum Projects, when everyone is new to Agile, testing should be handled by a team of tester rather than a single tester. They will collaborative and work on issues, which will make them comfortable in this process. Later on, they can independently handle different projects.
So, these were just some of the cultural challenges that teams face while adopting a SCRUM approach.
Posted by SCRUMstudy® on July 19, 2024
Categories: Agile SBOK® Guide Scrum Scrum Guide Scrum Team
The Scrum Master certification significantly enhances project adaptability by equipping professionals with the necessary skills to effectively implement Scrum practices. Certified Scrum Masters are trained to foster an environment of continuous improvement, enabling teams to respond swiftly and efficiently to changing project requirements and external conditions. Their expertise in facilitating agile processes, such as iterative development and regular feedback loops, ensures that projects remain aligned with stakeholder needs and market dynamics. This adaptability is crucial for maintaining project momentum and achieving desired outcomes in an ever-evolving business landscape. By promoting a culture of collaboration, transparency, and proactive problem-solving, Scrum Masters drive the successful delivery of projects, even amidst uncertainty and change.
Let’s take up an example to understand this. Mike is a Project Manager and his project is about to migrate to Scrum. For a very long time, Mike is working as a manager in his career. Mike has respected his team mates and trusted them to be responsible about their jobs. His ideology about the finest approach to obtain the outcomes is to develop a team of exceedingly driven professionals, set goals, take initiatives and ensure all needed resources towards their work are there without obstacles. The team looks up to Mike if they have any problems or concerns, as they feel quite at ease intimating project estimates to him because of no “Boss pressure”. He is always careful of their requirements with high importance. It has always been Mike’s goal to enable and support effective communication, prevent and resolve clashes, eliminate obstacles, and make certain maximum prominence into the project for all the involved business stakeholders.
Would Mike be a good Scrum Master for his team? Yes, he will be a good Scrum Master.
The product owner is equally vital as the Scrum Master. In the absence of an effective and efficient product owner, the project is unlikely to succeed. Preferably the role of product owner should be undertaken by the client, who isn’t always plausible or the client is very engrossed with something that, though formally it is the product owner but whom always finds availability at all times to the team a major inability.
In this situation, there is a necessity for a product owner, or substitution product owner, indigenous to the team. A likely candidate can be the project manager. Interacting and working with numerous business stakeholders to convert an incessant flow of change requests into a prioritized list is something the project manager can fare well as he would have prior experience on that.
Posted by SCRUMstudy® on July 19, 2024
Categories: Agile Continuous Integration Iterative Development Product Development
Agile Adaptability Tools are instrumental in facilitating flexibility and responsiveness within Agile frameworks. These tools serve as mechanisms to navigate the dynamic landscape of project development, enabling teams to swiftly adjust to changing requirements and market conditions. Key tools include adaptive planning techniques, such as Agile estimation and release planning, which allow teams to continuously refine and reprioritize tasks based on emerging insights. Additionally, iterative development practices, exemplified by frequent reviews and retrospectives, foster a culture of continuous improvement and adaptation. Collaboration tools like Kanban boards and daily stand-up meetings promote transparency and enhance communication, ensuring alignment across team members and stakeholders. By leveraging these Agile Adaptability Tools, organizations can effectively navigate uncertainty, maximize opportunities, and deliver value to customers in a rapidly evolving marketplace.
Agile Master Practices encapsulate principles and methodologies essential for effective Agile project management. These practices encompass a dynamic approach to project execution, emphasizing collaboration, adaptability, and continuous improvement. Key practices include fostering open communication within cross-functional teams, promoting iterative development cycles, and embracing change as a catalyst for innovation. Additionally, Agile Master Practices advocate for transparent decision-making processes, empowering teams to self-organize and take ownership of project outcomes.
Scrum agile practices encompass a set of principles and methodologies aimed at promoting flexibility, collaboration, and continuous improvement within project management. Key practices include iterative development cycles known as sprints, typically lasting two to four weeks, during which teams deliver incremental pieces of working software.
Project Management Institute’s “PMI Agile Certified Practitioner Exam Content Outline” organizes the tasks practitioners do when working in Agile environment into six domains. Their exam does not test specifically on the domains, so learning their grouping of tools and techniques and knowledge and skills will not be directly applicable to the language of the test. However, this organizational way of looking at Agile tools and tasks has been done to help practitioners learn and understand Agile better.
The six domains of Agile are:
Let’s discuss each domain in more detail.
Value-driven delivery
Creating value is at the core of any project, and Agile methods are designed with the core objective of delivering value on a knowledge worker project. While maximizing value, Agile also has tools and techniques to minimize risks that can erode value. Agile methods also place importance on the customer’s priorities and is designed to deliver elements that have the highest value to the customer first.
Assessing value –.
Planning value – We create a charter detailing the scope, objective, and other attributes of the project. We then use tools such as customer-valued prioritization, relative prioritization, and risk adjusted backlog while preparing the priority list. Which planning value, we also assess the contracting costs of the project.
Delivering value – After planning how we are going to deliver value, we focus on eliminating all activities that do not add value. We can use task and Kanban boards to schedule the backlog. Limiting the Work in Progress (WIP) reduces the potential for reworking and keeps the project going smoothly.
Confirming value – We have executed tasks and created value but is this what the customer wanted? We have to confirm the value we are delivering to know this. We demonstrate prototypes, simulate functionalities to help the customer test the product and see how they work.
Tracking and reporting value – It is not enough that we just deliver value. It is important that we regularly track the rate of delivery of value so that it can be communicated to business stakeholders. Cumulative flow diagrams and burn down graphs are an easy and informative way through which we can assess the development of the project.
Stakeholder engagement
Stakeholders in a project can be anybody who can negatively or positively impact a project. They can be business representatives, customers, the project manager, the development team, or external vendors contributing directly or indirectly to the project. Stakeholder engagement becomes important, because software development involves creating intangible products and the team must have a precise understanding of customer requirements.
Agile projects are subject to constant change which makes it essential that a clear and steady channel of communication is established. All stakeholders must be involved in the project to ensure that it stays on the right track. Teams can use tools such as wireframes, user stories, a user story backlog, and personas to verify their understanding of customer requirements.
Face-to-face communication is the most preferred method of communication on agile projects. They provide the maximum amount of information in the least amount of time. Information radiators such as burn down charts, cumulative flow diagrams, and velocity tracking charts allow us to determine progress of the project, which can be communicated to all the stakeholders.
Soft skills play an important role while engaging with stakeholders. Soft skills such as negotiating and active listening are necessary while dealing with customers. It is also essential that we be familiar with implementing soft skills such as facilitation methods, participatory decision models, and conflict resolution that are primarily concerned with managing teams.
When we talk of managing teams, our leadership skills play a crucial role. Servant leadership is an extremely effective way of leading teams. A servant leader encourages the team to excel by removing any obstacles, motivate and reward the team’s performance.
Boosting team performance
The third domain in Agile deals with boosting team performance practices. In software development, “people factors” incur the highest cost. Therefore, it is extremely important that we obtain the highest return on performance.
The process of forming a team is one of the determinants of success on a project. Building a team goes through the stages of forming (identifying potential team members and bringing them together), storming (the team collaborates and comes up with ideas), norming (teams form rules and normalize their working patterns), and performing (the team works together). During each of these phases, it is important for a leader to know when to play a supporting or directing role. For example, during the storming phase, conflicts can be frequent and the leader will have to step in to help the team members develop methodologies to resolve them.
To get the best out of a team, it should be self-organizing and self-directing. Allowing teams to be self-organizing and self-directing enables team members to manage complex tasks by themselves and figure out the best way to complete the tasks. This capitalizes on the team’s combined expertise and talent.
There are several activities that can help a team boost their performance on Agile projects. Daily stand-up meetings are a quick way to communicate the team’s performance status and identify present and potential issues. To overcome issues and improve continuously, teams might need to be mentored at different stages. During events such as iteration planning meetings or retrospectives, teams might need to be coached at a group level and mentoring can be provided for individual team members when the iteration is underway.
Brainstorming sessions can be used by teams to resolve issues, improve, and innovate processes. Because face-to-face communication is the ideal way to communicate on Agile projects, it is important that the team be located in a common area with space for whiteboards and other information radiators.
Adaptive Planning
Because extensive planning before the project is undertaken can be cumbersome and often does not add any real value, Agile calls for an adaptive approach to planning. Adaptive planning involves creating a basic plan and updating it as the project gets underway. Adaptive planning requires practitioners to maintain close collaboration with the customer to understand his or her requirements more accurately. Collaborative games such as remember the future, prune the product tree, buy a feature, and bang-for-the-buck can be used to help the development team understand customer requirements better.
To make timely deliveries, team members should calculate their estimates as accurately as possible factoring in all diversions and constraints. Wideband Delphi and Ideal Time are some of the techniques which can help teams arrive at an accurate estimate. While estimating the cost of the project, the figures should be presented in ranges as they seem more credible than pin-point figures that can have an air of false confidence.
Iteration and release planning is a vital part of adaptive planning. Releases are bundles of functionality that can be delivered to a customer. While planning a release, the Product Owner/manager, development team, and Agile Expert can use a velocity chart to determine how many features can be completed by the team in a given time. While planning iterations, it important to have a fixed priority list at the beginning of the planning session. Team members have the final say on how much work can be completed, while the product owner gets the final say on the priority of the items included for the iteration. Availability of team members needs to be factored in while planning iterations.
Problem Detection and Resolution
A common saying is, “A stitch in time saves nine,” and this couldn’t be more apt to explain how Agile methods deal with problems. If ignored, problems can have a devastating effect on the project as they not only increase the burden of rework; they make the team fall behind in its plans. It is a double whammy for the team when this happens as it takes twice the resources. Agile practices aids in detecting problems as early as possible and fixing them while they are still small.
Detecting problems is the first step to resolving them. Daily stand-up meetings are an excellent way to identify any issues that team members are facing. Teams can also track issues by calculating cycle times for tasks. If the cycle time is too high, it might indicate a potential problem or that the team has undertaken more work than it can complete. Limiting work in progress can help monitor the project timeline better and track problems more easily. Despite our best efforts, some defects may make their way through to the final product. Escaped defects are the most expensive to fix. Teams can track escaped defects on a graph to analyze trends. This can help refine quality control processes.
Alistair Cockburn describes “failure modes and alternatives,” that are related to the human aspect of performance. Cockburn says that people fail because they can be inconsistent at following a technique, are creatures of habit and prefer to invent new ways than modify existing reliable methods. To counter “failure modes” Cockburn advises that teams should inculcate discipline, receive feedback regularly, and assign work based on personalities of individual team members.
Resolving issues that are identified is the next step. Continuous integration of new code, as and when it is developed, in a repository can help overcome the issues that we find with integration. Validating progress at frequent intervals and at different levels can help us be confident that our work is error-free.
In software development, commonly used techniques are Test-Driven Development (TDD) and Acceptance Test-Driven Development (ATDD). These methods primarily involve writing the tests before any code is written. The codes are written until they pass the tests. Codes might then be “refactored” if necessary, which involves refining the design without altering its behavior.
Continuous Improvement
New insights and learning gained on a traditional project is typically gathered at the end of the project cycle. These insights might not be of much help on the next project unless the two are very similar. That learning could have had more value, if it had been used on the project in which it was learned. Agile methodology seeks to continuously improve throughout the project and encourage applying lessons to the development process as and when we learn it. Retrospectives at the end of each iteration makes the lessons learned available for the very next iteration.
A retrospective typically lasts for about two hours during which time the team gathers data about the different challenges that it faced and the various lessons learned while solving them. The learning is analyzed to see if there exists underlying patterns or any insights. Armed with these patterns and insights, the team plans the next iteration.
As part of continuous improvement, team members should be encouraged to share knowledge they acquire, with other team members. One of the reasons colocation is stressed in Agile projects is because it provides a platform for knowledge sharing through face-to-face communication. To encourage knowledge sharing, team velocity can be tracked at a team level rather than measuring it at an individual level, so that team members are motivated to help each other.
We might be required to tailor agile practices to suit our needs; however, one must careful while doing so. Agile practices have been crafted into a delicate web of interdependent practices and disturbing one can affect other practices. We should be adept at using agile practices before we make any modifications. It might be tempting at times to blame the tools if our work is not going accordingly when the real problem lies in us. We should carefully examine our motives to change practices before we make any alterations.
Posted by SCRUMstudy® on July 02, 2024
Categories: Agile Continuous Integration Iterative Development Product Development
Agile Adaptability Tools are instrumental in facilitating flexibility and responsiveness within Agile frameworks. These tools serve as mechanisms to navigate the dynamic landscape of project development, enabling teams to swiftly adjust to changing requirements and market conditions. Key tools include adaptive planning techniques, such as Agile estimation and release planning, which allow teams to continuously refine and reprioritize tasks based on emerging insights. Additionally, iterative development practices, exemplified by frequent reviews and retrospectives, foster a culture of continuous improvement and adaptation. Collaboration tools like Kanban boards and daily stand-up meetings promote transparency and enhance communication, ensuring alignment across team members and stakeholders. By leveraging these Agile Adaptability Tools, organizations can effectively navigate uncertainty, maximize opportunities, and deliver value to customers in a rapidly evolving marketplace.
Agile Master Practices encapsulate principles and methodologies essential for effective Agile project management. These practices encompass a dynamic approach to project execution, emphasizing collaboration, adaptability, and continuous improvement. Key practices include fostering open communication within cross-functional teams, promoting iterative development cycles, and embracing change as a catalyst for innovation. Additionally, Agile Master Practices advocate for transparent decision-making processes, empowering teams to self-organize and take ownership of project outcomes.
Scrum agile practices encompass a set of principles and methodologies aimed at promoting flexibility, collaboration, and continuous improvement within project management. Key practices include iterative development cycles known as sprints, typically lasting two to four weeks, during which teams deliver incremental pieces of working software.
Project Management Institute’s “PMI Agile Certified Practitioner Exam Content Outline” organizes the tasks practitioners do when working in Agile environment into six domains. Their exam does not test specifically on the domains, so learning their grouping of tools and techniques and knowledge and skills will not be directly applicable to the language of the test. However, this organizational way of looking at Agile tools and tasks has been done to help practitioners learn and understand Agile better.
The six domains of Agile are:
Let’s discuss each domain in more detail.
Value-driven delivery
Creating value is at the core of any project, and Agile methods are designed with the core objective of delivering value on a knowledge worker project. While maximizing value, Agile also has tools and techniques to minimize risks that can erode value. Agile methods also place importance on the customer’s priorities and is designed to deliver elements that have the highest value to the customer first.
Assessing value –.
Planning value – We create a charter detailing the scope, objective, and other attributes of the project. We then use tools such as customer-valued prioritization, relative prioritization, and risk adjusted backlog while preparing the priority list. Which planning value, we also assess the contracting costs of the project.
Delivering value – After planning how we are going to deliver value, we focus on eliminating all activities that do not add value. We can use task and Kanban boards to schedule the backlog. Limiting the Work in Progress (WIP) reduces the potential for reworking and keeps the project going smoothly.
Confirming value – We have executed tasks and created value but is this what the customer wanted? We have to confirm the value we are delivering to know this. We demonstrate prototypes, simulate functionalities to help the customer test the product and see how they work.
Tracking and reporting value – It is not enough that we just deliver value. It is important that we regularly track the rate of delivery of value so that it can be communicated to business stakeholders. Cumulative flow diagrams and burn down graphs are an easy and informative way through which we can assess the development of the project.
Stakeholder engagement
Stakeholders in a project can be anybody who can negatively or positively impact a project. They can be business representatives, customers, the project manager, the development team, or external vendors contributing directly or indirectly to the project. Stakeholder engagement becomes important, because software development involves creating intangible products and the team must have a precise understanding of customer requirements.
Agile projects are subject to constant change which makes it essential that a clear and steady channel of communication is established. All stakeholders must be involved in the project to ensure that it stays on the right track. Teams can use tools such as wireframes, user stories, a user story backlog, and personas to verify their understanding of customer requirements.
Face-to-face communication is the most preferred method of communication on agile projects. They provide the maximum amount of information in the least amount of time. Information radiators such as burn down charts, cumulative flow diagrams, and velocity tracking charts allow us to determine progress of the project, which can be communicated to all the stakeholders.
Soft skills play an important role while engaging with stakeholders. Soft skills such as negotiating and active listening are necessary while dealing with customers. It is also essential that we be familiar with implementing soft skills such as facilitation methods, participatory decision models, and conflict resolution that are primarily concerned with managing teams.
When we talk of managing teams, our leadership skills play a crucial role. Servant leadership is an extremely effective way of leading teams. A servant leader encourages the team to excel by removing any obstacles, motivate and reward the team’s performance.
Boosting team performance
The third domain in Agile deals with boosting team performance practices. In software development, “people factors” incur the highest cost. Therefore, it is extremely important that we obtain the highest return on performance.
The process of forming a team is one of the determinants of success on a project. Building a team goes through the stages of forming (identifying potential team members and bringing them together), storming (the team collaborates and comes up with ideas), norming (teams form rules and normalize their working patterns), and performing (the team works together). During each of these phases, it is important for a leader to know when to play a supporting or directing role. For example, during the storming phase, conflicts can be frequent and the leader will have to step in to help the team members develop methodologies to resolve them.
To get the best out of a team, it should be self-organizing and self-directing. Allowing teams to be self-organizing and self-directing enables team members to manage complex tasks by themselves and figure out the best way to complete the tasks. This capitalizes on the team’s combined expertise and talent.
There are several activities that can help a team boost their performance on Agile projects. Daily stand-up meetings are a quick way to communicate the team’s performance status and identify present and potential issues. To overcome issues and improve continuously, teams might need to be mentored at different stages. During events such as iteration planning meetings or retrospectives, teams might need to be coached at a group level and mentoring can be provided for individual team members when the iteration is underway.
Brainstorming sessions can be used by teams to resolve issues, improve, and innovate processes. Because face-to-face communication is the ideal way to communicate on Agile projects, it is important that the team be located in a common area with space for whiteboards and other information radiators.
Adaptive Planning
Because extensive planning before the project is undertaken can be cumbersome and often does not add any real value, Agile calls for an adaptive approach to planning. Adaptive planning involves creating a basic plan and updating it as the project gets underway. Adaptive planning requires practitioners to maintain close collaboration with the customer to understand his or her requirements more accurately. Collaborative games such as remember the future, prune the product tree, buy a feature, and bang-for-the-buck can be used to help the development team understand customer requirements better.
To make timely deliveries, team members should calculate their estimates as accurately as possible factoring in all diversions and constraints. Wideband Delphi and Ideal Time are some of the techniques which can help teams arrive at an accurate estimate. While estimating the cost of the project, the figures should be presented in ranges as they seem more credible than pin-point figures that can have an air of false confidence.
Iteration and release planning is a vital part of adaptive planning. Releases are bundles of functionality that can be delivered to a customer. While planning a release, the Product Owner/manager, development team, and Agile Expert can use a velocity chart to determine how many features can be completed by the team in a given time. While planning iterations, it important to have a fixed priority list at the beginning of the planning session. Team members have the final say on how much work can be completed, while the product owner gets the final say on the priority of the items included for the iteration. Availability of team members needs to be factored in while planning iterations.
Problem Detection and Resolution
A common saying is, “A stitch in time saves nine,” and this couldn’t be more apt to explain how Agile methods deal with problems. If ignored, problems can have a devastating effect on the project as they not only increase the burden of rework; they make the team fall behind in its plans. It is a double whammy for the team when this happens as it takes twice the resources. Agile practices aids in detecting problems as early as possible and fixing them while they are still small.
Detecting problems is the first step to resolving them. Daily stand-up meetings are an excellent way to identify any issues that team members are facing. Teams can also track issues by calculating cycle times for tasks. If the cycle time is too high, it might indicate a potential problem or that the team has undertaken more work than it can complete. Limiting work in progress can help monitor the project timeline better and track problems more easily. Despite our best efforts, some defects may make their way through to the final product. Escaped defects are the most expensive to fix. Teams can track escaped defects on a graph to analyze trends. This can help refine quality control processes.
Alistair Cockburn describes “failure modes and alternatives,” that are related to the human aspect of performance. Cockburn says that people fail because they can be inconsistent at following a technique, are creatures of habit and prefer to invent new ways than modify existing reliable methods. To counter “failure modes” Cockburn advises that teams should inculcate discipline, receive feedback regularly, and assign work based on personalities of individual team members.
Resolving issues that are identified is the next step. Continuous integration of new code, as and when it is developed, in a repository can help overcome the issues that we find with integration. Validating progress at frequent intervals and at different levels can help us be confident that our work is error-free.
In software development, commonly used techniques are Test-Driven Development (TDD) and Acceptance Test-Driven Development (ATDD). These methods primarily involve writing the tests before any code is written. The codes are written until they pass the tests. Codes might then be “refactored” if necessary, which involves refining the design without altering its behavior.
Continuous Improvement
New insights and learning gained on a traditional project is typically gathered at the end of the project cycle. These insights might not be of much help on the next project unless the two are very similar. That learning could have had more value, if it had been used on the project in which it was learned. Agile methodology seeks to continuously improve throughout the project and encourage applying lessons to the development process as and when we learn it. Retrospectives at the end of each iteration makes the lessons learned available for the very next iteration.
A retrospective typically lasts for about two hours during which time the team gathers data about the different challenges that it faced and the various lessons learned while solving them. The learning is analyzed to see if there exists underlying patterns or any insights. Armed with these patterns and insights, the team plans the next iteration.
As part of continuous improvement, team members should be encouraged to share knowledge they acquire, with other team members. One of the reasons colocation is stressed in Agile projects is because it provides a platform for knowledge sharing through face-to-face communication. To encourage knowledge sharing, team velocity can be tracked at a team level rather than measuring it at an individual level, so that team members are motivated to help each other.
We might be required to tailor agile practices to suit our needs; however, one must careful while doing so. Agile practices have been crafted into a delicate web of interdependent practices and disturbing one can affect other practices. We should be adept at using agile practices before we make any modifications. It might be tempting at times to blame the tools if our work is not going accordingly when the real problem lies in us. We should carefully examine our motives to change practices before we make any alterations.
Posted by SCRUMstudy® on July 02, 2024
Categories: Agile Continuous Integration Iterative Development Product Development
Agile Adaptability Tools are instrumental in facilitating flexibility and responsiveness within Agile frameworks. These tools serve as mechanisms to navigate the dynamic landscape of project development, enabling teams to swiftly adjust to changing requirements and market conditions. Key tools include adaptive planning techniques, such as Agile estimation and release planning, which allow teams to continuously refine and reprioritize tasks based on emerging insights. Additionally, iterative development practices, exemplified by frequent reviews and retrospectives, foster a culture of continuous improvement and adaptation. Collaboration tools like Kanban boards and daily stand-up meetings promote transparency and enhance communication, ensuring alignment across team members and stakeholders. By leveraging these Agile Adaptability Tools, organizations can effectively navigate uncertainty, maximize opportunities, and deliver value to customers in a rapidly evolving marketplace.
Agile Master Practices encapsulate principles and methodologies essential for effective Agile project management. These practices encompass a dynamic approach to project execution, emphasizing collaboration, adaptability, and continuous improvement. Key practices include fostering open communication within cross-functional teams, promoting iterative development cycles, and embracing change as a catalyst for innovation. Additionally, Agile Master Practices advocate for transparent decision-making processes, empowering teams to self-organize and take ownership of project outcomes.
Scrum agile practices encompass a set of principles and methodologies aimed at promoting flexibility, collaboration, and continuous improvement within project management. Key practices include iterative development cycles known as sprints, typically lasting two to four weeks, during which teams deliver incremental pieces of working software.
Project Management Institute’s “PMI Agile Certified Practitioner Exam Content Outline” organizes the tasks practitioners do when working in Agile environment into six domains. Their exam does not test specifically on the domains, so learning their grouping of tools and techniques and knowledge and skills will not be directly applicable to the language of the test. However, this organizational way of looking at Agile tools and tasks has been done to help practitioners learn and understand Agile better.
The six domains of Agile are:
Let’s discuss each domain in more detail.
Value-driven delivery
Creating value is at the core of any project, and Agile methods are designed with the core objective of delivering value on a knowledge worker project. While maximizing value, Agile also has tools and techniques to minimize risks that can erode value. Agile methods also place importance on the customer’s priorities and is designed to deliver elements that have the highest value to the customer first.
Assessing value –.
Planning value – We create a charter detailing the scope, objective, and other attributes of the project. We then use tools such as customer-valued prioritization, relative prioritization, and risk adjusted backlog while preparing the priority list. Which planning value, we also assess the contracting costs of the project.
Delivering value – After planning how we are going to deliver value, we focus on eliminating all activities that do not add value. We can use task and Kanban boards to schedule the backlog. Limiting the Work in Progress (WIP) reduces the potential for reworking and keeps the project going smoothly.
Confirming value – We have executed tasks and created value but is this what the customer wanted? We have to confirm the value we are delivering to know this. We demonstrate prototypes, simulate functionalities to help the customer test the product and see how they work.
Tracking and reporting value – It is not enough that we just deliver value. It is important that we regularly track the rate of delivery of value so that it can be communicated to business stakeholders. Cumulative flow diagrams and burn down graphs are an easy and informative way through which we can assess the development of the project.
Stakeholder engagement
Stakeholders in a project can be anybody who can negatively or positively impact a project. They can be business representatives, customers, the project manager, the development team, or external vendors contributing directly or indirectly to the project. Stakeholder engagement becomes important, because software development involves creating intangible products and the team must have a precise understanding of customer requirements.
Agile projects are subject to constant change which makes it essential that a clear and steady channel of communication is established. All stakeholders must be involved in the project to ensure that it stays on the right track. Teams can use tools such as wireframes, user stories, a user story backlog, and personas to verify their understanding of customer requirements.
Face-to-face communication is the most preferred method of communication on agile projects. They provide the maximum amount of information in the least amount of time. Information radiators such as burn down charts, cumulative flow diagrams, and velocity tracking charts allow us to determine progress of the project, which can be communicated to all the stakeholders.
Soft skills play an important role while engaging with stakeholders. Soft skills such as negotiating and active listening are necessary while dealing with customers. It is also essential that we be familiar with implementing soft skills such as facilitation methods, participatory decision models, and conflict resolution that are primarily concerned with managing teams.
When we talk of managing teams, our leadership skills play a crucial role. Servant leadership is an extremely effective way of leading teams. A servant leader encourages the team to excel by removing any obstacles, motivate and reward the team’s performance.
Boosting team performance
The third domain in Agile deals with boosting team performance practices. In software development, “people factors” incur the highest cost. Therefore, it is extremely important that we obtain the highest return on performance.
The process of forming a team is one of the determinants of success on a project. Building a team goes through the stages of forming (identifying potential team members and bringing them together), storming (the team collaborates and comes up with ideas), norming (teams form rules and normalize their working patterns), and performing (the team works together). During each of these phases, it is important for a leader to know when to play a supporting or directing role. For example, during the storming phase, conflicts can be frequent and the leader will have to step in to help the team members develop methodologies to resolve them.
To get the best out of a team, it should be self-organizing and self-directing. Allowing teams to be self-organizing and self-directing enables team members to manage complex tasks by themselves and figure out the best way to complete the tasks. This capitalizes on the team’s combined expertise and talent.
There are several activities that can help a team boost their performance on Agile projects. Daily stand-up meetings are a quick way to communicate the team’s performance status and identify present and potential issues. To overcome issues and improve continuously, teams might need to be mentored at different stages. During events such as iteration planning meetings or retrospectives, teams might need to be coached at a group level and mentoring can be provided for individual team members when the iteration is underway.
Brainstorming sessions can be used by teams to resolve issues, improve, and innovate processes. Because face-to-face communication is the ideal way to communicate on Agile projects, it is important that the team be located in a common area with space for whiteboards and other information radiators.
Adaptive Planning
Because extensive planning before the project is undertaken can be cumbersome and often does not add any real value, Agile calls for an adaptive approach to planning. Adaptive planning involves creating a basic plan and updating it as the project gets underway. Adaptive planning requires practitioners to maintain close collaboration with the customer to understand his or her requirements more accurately. Collaborative games such as remember the future, prune the product tree, buy a feature, and bang-for-the-buck can be used to help the development team understand customer requirements better.
To make timely deliveries, team members should calculate their estimates as accurately as possible factoring in all diversions and constraints. Wideband Delphi and Ideal Time are some of the techniques which can help teams arrive at an accurate estimate. While estimating the cost of the project, the figures should be presented in ranges as they seem more credible than pin-point figures that can have an air of false confidence.
Iteration and release planning is a vital part of adaptive planning. Releases are bundles of functionality that can be delivered to a customer. While planning a release, the Product Owner/manager, development team, and Agile Expert can use a velocity chart to determine how many features can be completed by the team in a given time. While planning iterations, it important to have a fixed priority list at the beginning of the planning session. Team members have the final say on how much work can be completed, while the product owner gets the final say on the priority of the items included for the iteration. Availability of team members needs to be factored in while planning iterations.
Problem Detection and Resolution
A common saying is, “A stitch in time saves nine,” and this couldn’t be more apt to explain how Agile methods deal with problems. If ignored, problems can have a devastating effect on the project as they not only increase the burden of rework; they make the team fall behind in its plans. It is a double whammy for the team when this happens as it takes twice the resources. Agile practices aids in detecting problems as early as possible and fixing them while they are still small.
Detecting problems is the first step to resolving them. Daily stand-up meetings are an excellent way to identify any issues that team members are facing. Teams can also track issues by calculating cycle times for tasks. If the cycle time is too high, it might indicate a potential problem or that the team has undertaken more work than it can complete. Limiting work in progress can help monitor the project timeline better and track problems more easily. Despite our best efforts, some defects may make their way through to the final product. Escaped defects are the most expensive to fix. Teams can track escaped defects on a graph to analyze trends. This can help refine quality control processes.
Alistair Cockburn describes “failure modes and alternatives,” that are related to the human aspect of performance. Cockburn says that people fail because they can be inconsistent at following a technique, are creatures of habit and prefer to invent new ways than modify existing reliable methods. To counter “failure modes” Cockburn advises that teams should inculcate discipline, receive feedback regularly, and assign work based on personalities of individual team members.
Resolving issues that are identified is the next step. Continuous integration of new code, as and when it is developed, in a repository can help overcome the issues that we find with integration. Validating progress at frequent intervals and at different levels can help us be confident that our work is error-free.
In software development, commonly used techniques are Test-Driven Development (TDD) and Acceptance Test-Driven Development (ATDD). These methods primarily involve writing the tests before any code is written. The codes are written until they pass the tests. Codes might then be “refactored” if necessary, which involves refining the design without altering its behavior.
Continuous Improvement
New insights and learning gained on a traditional project is typically gathered at the end of the project cycle. These insights might not be of much help on the next project unless the two are very similar. That learning could have had more value, if it had been used on the project in which it was learned. Agile methodology seeks to continuously improve throughout the project and encourage applying lessons to the development process as and when we learn it. Retrospectives at the end of each iteration makes the lessons learned available for the very next iteration.
A retrospective typically lasts for about two hours during which time the team gathers data about the different challenges that it faced and the various lessons learned while solving them. The learning is analyzed to see if there exists underlying patterns or any insights. Armed with these patterns and insights, the team plans the next iteration.
As part of continuous improvement, team members should be encouraged to share knowledge they acquire, with other team members. One of the reasons colocation is stressed in Agile projects is because it provides a platform for knowledge sharing through face-to-face communication. To encourage knowledge sharing, team velocity can be tracked at a team level rather than measuring it at an individual level, so that team members are motivated to help each other.
We might be required to tailor agile practices to suit our needs; however, one must careful while doing so. Agile practices have been crafted into a delicate web of interdependent practices and disturbing one can affect other practices. We should be adept at using agile practices before we make any modifications. It might be tempting at times to blame the tools if our work is not going accordingly when the real problem lies in us. We should carefully examine our motives to change practices before we make any alterations.