This Festive Season, enjoy 10% discount on all courses Use Coupon NY10 Click to Copy

Search

Decision About Which Agile Method To Use - A Perspective

Introduction:Agile methods have gained widespread acceptance in software development organizations for formulation and development of solutions for enhancing existing products or creating new ones. The method has been very effective in the continuous delivery of new and effective solutions.Organizations trying to introduce Agile methodologies, in the beginning, are faced with a choice of which type of Agile methodology is best suited for their environment and types of project work. You may learn more about the challenges encountered by the first-time Agile organizations here.The Agile Manifesto favors the delivery of working software in comparison to comprehensive documentation. There is a constant emphasis on a relation between organization and developers rooted in-Trust,Integrity, andTransparency.It may not be a huge shift, but is still a powerful challenge for many companies. The team should be trained well, should be aware of Agile concepts and should have the required tools needed to perform. A team of experienced and skilled developers is more efficient to take decisions when compared to a less experienced team and understands customer commitment much better. Agile delivery values direct interaction and business user collaboration instead of uneven communication in the life cycle  at fixed points. Effective involvement of the  business reduces the delivered features risk that do not meet customer requirements.How to decide the best Agile methodology that is suitable for an organization?Despite the fact that every Agile methodology offers incremental and iterative delivery of software, the differences lie in the way artifacts produced and each methodology is executed.Let us discuss in detail the most popular Agile Methodologies:Scrum: Scrum is focused on self-organizing teams. Its core principles are aligned with client-driven adaptive planning. Scrum method’s main priority is the delivery of working software in no more than 30 days. Delivered software needs to be in releasable shape.Minimum documentation is supported. Scrum is most used in the Agile framework. Its widespread usage and benefits have made it the most popular Agile method.Extreme Programming(XP): It keeps things simple and concentrates on the continuous implementation of best practices such as-Ongoing testingRefactoringCode reviews (pair programming)Continuous integration.In this method, there is a focus on the developer’s capability and getting into the development of the working prototype as fast as possible.Feature Driven Development (FDD): Breaks down the delivery of a larger product into small features. Typically, FDD is characterised by-Short iteration cyclesSimple processesSuitability for predictable evolutionThe method needs experienced resources to define the required features in great details to make them implementable.Kanban: It is based on Toyota’s just-in-time (JIT) production system. The salient features are as follows-Focuses on eliminating bottlenecksIncredibly simple and powerful Kanban boardsKanban uses Flow and visual methods to bring elements of agile in the overall development process.Makes elaborate use of visual tools.Typical usage involves a space in the office area with printed boards showing status of the activities as shown in the diagram below.Lean Development: Lean Development concentrates on offering value for money. It recommends amplifying learning, avoiding unnecessary errors, delivering as early as possible and deciding as late as possible. The first and foremost principle of lean project management is diminishing waste in an established process. It is more frequently applied to production and manufacturing than in product development. Lean mainly focuses on key process improvement points, such as standardizing means of production and reducing bottlenecks. Although Lean has a different application than the Agile methodology, there are certain common elements such as-Valuing a strong facilitator andPipeliningDSDM: It is developed from a business perspective and lays a strong emphasis on project management. The plans produce based on increments.Sometimes, a combination of multiple methods is the best solution. For example, a combination of Scrum and Kanban is a preferred combination for projects that need the iterative approach of Scrum and the visual elements of Kanban. Similarly, pair programming aspects of Extreme programming (XP) are borrowed for Scrum development teams. It is also advisable that, Agile is not a suitable methodology for some projects. This also should be kept in mind while evaluating an appropriate Agile methodology.In Summary:Agile method to be used for an organization depends on the objectives and desired outcomes. The methods can be implemented either in an existing program or for a new one. Current state and resources available will be of prime importance in deciding the approach and the timeline of implementation. It has been proven time and again that Agile methodologies help an organization to improve the speed of product delivery and quality. They also help establish clear communication channels within the organization and with critical customers and have an approach and method to incorporate customer feedback quickly in the product roadmap.
Rated 4.0/5 based on 0 customer reviews

Decision About Which Agile Method To Use - A Perspective

231
  • by Raju Dhole
  • 12th Sep, 2018
  • Last updated on 15th Jan, 2019
  • 3 mins read
Decision About Which Agile Method To Use - A Perspective

Introduction:

Agile methods have gained widespread acceptance in software development organizations for formulation and development of solutions for enhancing existing products or creating new ones. The method has been very effective in the continuous delivery of new and effective solutions.

Organizations trying to introduce Agile methodologies, in the beginning, are faced with a choice of which type of Agile methodology is best suited for their environment and types of project work. You may learn more about the challenges encountered by the first-time Agile organizations here.

The Agile Manifesto favors the delivery of working software in comparison to comprehensive documentation. There is a constant emphasis on a relation between organization and developers rooted in-

  • Trust,
  • Integrity, and
  • Transparency.

It may not be a huge shift, but is still a powerful challenge for many companies. The team should be trained well, should be aware of Agile concepts and should have the required tools needed to perform. A team of experienced and skilled developers is more efficient to take decisions when compared to a less experienced team and understands customer commitment much better. Agile delivery values direct interaction and business user collaboration instead of uneven communication in the life cycle  at fixed points. Effective involvement of the  business reduces the delivered features risk that do not meet customer requirements.

How to decide the best Agile methodology that is suitable for an organization?
Agile methodology that is suitable for an organizationDespite the fact that every Agile methodology offers incremental and iterative delivery of software, the differences lie in the way artifacts produced and each methodology is executed.

Let us discuss in detail the most popular Agile Methodologies:

Scrum: Scrum is focused on self-organizing teams. Its core principles are aligned with client-driven adaptive planning. Scrum method’s main priority is the delivery of working software in no more than 30 days. Delivered software needs to be in releasable shape.

Minimum documentation is supported. Scrum is most used in the Agile framework. Its widespread usage and benefits have made it the most popular Agile method.
Agile Scrum Framework

Extreme Programming(XP): It keeps things simple and concentrates on the continuous implementation of best practices such as-

  • Ongoing testing
  • Refactoring
  • Code reviews (pair programming)
  • Continuous integration.

In this method, there is a focus on the developer’s capability and getting into the development of the working prototype as fast as possible.

Feature Driven Development (FDD): Breaks down the delivery of a larger product into small features. Typically, FDD is characterised by-

  • Short iteration cycles
  • Simple processes
  • Suitability for predictable evolution

The method needs experienced resources to define the required features in great details to make them implementable.

Kanban: It is based on Toyota’s just-in-time (JIT) production system. The salient features are as follows-

  • Focuses on eliminating bottlenecks
  • Incredibly simple and powerful Kanban boards
  • Kanban uses Flow and visual methods to bring elements of agile in the overall development process.
  • Makes elaborate use of visual tools.
  • Typical usage involves a space in the office area with printed boards showing status of the activities as shown in the diagram below.

Feature Driven Development Lean Development: Lean Development concentrates on offering value for money. It recommends amplifying learning, avoiding unnecessary errors, delivering as early as possible and deciding as late as possible. The first and foremost principle of lean project management is diminishing waste in an established process. It is more frequently applied to production and manufacturing than in product development. Lean mainly focuses on key process improvement points, such as standardizing means of production and reducing bottlenecks. Although Lean has a different application than the Agile methodology, there are certain common elements such as-

  • Valuing a strong facilitator and
  • Pipelining

DSDM: It is developed from a business perspective and lays a strong emphasis on project management. The plans produce based on increments.

Sometimes, a combination of multiple methods is the best solution. For example, a combination of Scrum and Kanban is a preferred combination for projects that need the iterative approach of Scrum and the visual elements of Kanban. Similarly, pair programming aspects of Extreme programming (XP) are borrowed for Scrum development teams. It is also advisable that, Agile is not a suitable methodology for some projects. This also should be kept in mind while evaluating an appropriate Agile methodology.

In Summary:

Agile method to be used for an organization depends on the objectives and desired outcomes. The methods can be implemented either in an existing program or for a new one. Current state and resources available will be of prime importance in deciding the approach and the timeline of implementation. It has been proven time and again that Agile methodologies help an organization to improve the speed of product delivery and quality. They also help establish clear communication channels within the organization and with critical customers and have an approach and method to incorporate customer feedback quickly in the product roadmap.

Raju

Raju Dhole

Blog Author

Raju has 23+ years of IT Experience. He has a strong and diverse background in program, IT delivery, and financial management. He is an expert in project delivery using Agile methodologies and DevOps framework. He is a Recognized leader in innovation and transforming global teams. A strong communicator, he has proven ability to interact with multicultural and multi-location teams.  Raju has worked in multiple roles in Delivery Management, Client Relationship Management, Transition Management, Pre Sales, Business Strategy and Leadership Mentoring. 

Join the Discussion

Your email address will not be published. Required fields are marked *

Suggested Blogs

Product Backlog Refinement in Scrum

Product Backlog Refinement, also referred to as Product Backlog Grooming, is a method for keeping the backlog updated, clean and orderly. It is a basic process in Scrum. PBR is a collaborative discussion process which starts at the end of one sprint to confirm whether the backlog is ready for the next sprint. Backlog can be defined as a set of user stories which are not present in the current sprint that defines project’s scope context. The stories which are left unattended, may interfere with the functioning of the development team.When this happens, the status of user stories will not be clear, and even the team can lose focus and fail to deliver within the project completion date. The backlog grooming meeting is attended by the scrum master, who facilitates everything for team members, the team and the product owner. They decide among the top items from the product backlog. The team comprises mainly of Developers, testers and Scrum Masters. The team can raise queries during the sprint planning session if they find any unresolved issue. The expected doubts can arise in the following forms : How to handle the situation if the user enters invalid data? Which part of the system are the users authorized to operate on? For the product owner, it will be easy to get the conclusion over the queries, by asking these questions in the early stages. If there is a question which is unanswered by too many people, it is time to make some changes in your backlog items by curating higher priority items to the top of the list and assigning highest priority to the unanswered questions. The Objective of PBR meeting: A lot of time is saved at sprint planning meetings, if the backlogs are well maintained. If the backlog item is clearly specified in the acceptance criteria and cross-checked properly by the team members, the planning process can be accomplished prior to the meeting. PBR offers the team members the opportunity to interact with each other regarding stories. Why is PBR important?  PBR and its sessions are important mainly due to the following features- It increases the efficiency of the team by reducing uncertainty Properly refined stories are easy to estimate, test and implement. PBR session increases the efficiency of the team due to the knowledge shared among the team members. If PBR meeting is maintained properly, it helps reduce the time for a Sprint planning meeting. The Product Backlog grooming can be made effective if the following aspects are considered- Do not schedule backlog refinement meeting during the first and last 20% of the Sprint Planning session. Backlog refinement meeting should be considered as the first part of Sprint Planning. The backlog items’ list should be well understood by the PO, or development team member to work well in the meeting. Make sure that the set of predefined acceptance tests are present. Keep an eye on the meeting goals. Make sure to assign action items for any unknown thing. Do remember that the backlog items are a collaboration between the PO and the team. Feel free to break the product backlog items during the meeting. After the product backlog refinement meeting, the team can update the Product Backlog items in line, based on the discussions held. Finally, you can get a potentially shippable product, ready to be deployed in the market.
Rated 4.0/5 based on 20 customer reviews
2313
Product Backlog Refinement in Scrum

Product Backlog Refinement, also referred to as Pr... Read More

4 Tips To Pass Agile Practitioner Exam

There are many companies in the globe that are adopting Agile project management methodology. This is mainly due to the various benefits provided by this methodology such as breaking down large tasks into smaller parts, continuously evaluating the various stages of the project. The techniques in Agile also adhere to the various demands of the customer. Since money is a major factor for any organisation, Agile also aids in the preparation of the budget for every stage of the product. In order to successfully implement Agile principles in a project, you will need PMI ACP certification. You will have to undergo PMI ACP training in order to write the certification exam. For the training, you can either attend PMI ACP certification training in a classroom or opt for PMI-ACP training online. In order to successfully pass the certification exam, follow the steps mentioned below. 1) Time Management Time management is key to carry out any task. Ensure that you do not start preparing for the examination a day or two before the examination date. This examination cannot be aced by last minute preparations. If you’re actually serious about the exam, start preparing for it at least 3 months in advance. You need not spend 5-6 hours daily on your preparations. 2-3 hours on a daily basis for 2.5-3 months should be sufficient to ace the exam. The material and concepts covered in the Agile Practitioner Exam is extensive. You also need to have in-depth of many concepts in order to solve the difficult questions in the examination. Ensure that you spend more time in the preparation of these concepts. In order to thoroughly complete the preparation for all the necessary concepts, you will need to refer various study materials. It is vital that you allot sufficient time to each of these resources. 2) Practice papers Once you’re thorough with all the concepts necessary for the Agile Practitioner Exam, you can start attempting practice papers. Practice papers contain questions that are asked in the actual examination. There are many websites that offer free practice papers. Ensure that you sit in a quite environment and time yourself in order to get a feel of the actual examination. Following such a procedure will ensure that you are less tensed on the day of the exam and that you can confidently complete the examination. If you feel that you’re proficient in a few topics and want to test yourself on those topics only, there are concept-specific questions available online. These questions will help you test your knowledge on the selected topics. 3) Understand the concepts Many candidates who take up the Agile Practitioner Exam tend to memorise the difficult concepts instead of thoroughly understanding them. This might help you for a short period but, in the long run it will do more damage than good. You will definitely forget the concept in the examination and will not be able to solve complex problems because you haven’t understood the basics. Hence, it is vital that you understand the basics in order to ace the examination. 4) Forum There are many support groups and forums available on the web that are meant for candidates taking up the Agile Practitioner Exam. You can find the PMI-ACP Support Group on LinkedIn and various other study groups which consist of active members who have either written the Agile Practitioner Exam or are planning to give it soon. With the help of this platform, you can seek help to understand the concepts that are difficult for you and in return you can answer questions in the concepts that you find easy to solve. These groups are helpful for anyone writing the examination for the first time. At the end of the day, it doesn’t matter if you have 100 different study materials or spent 100 hours for the preparations for the exam. The only things that matter are the number of concepts you clearly understand and the quality of your learning in the hours you spent. These are the actual factors that make a difference on the day of the exam. Ensure that you do not study new concepts in the eleventh hour as this will only lead to confusion and not better results.
Rated 4.0/5 based on 20 customer reviews
1046
4 Tips To Pass Agile Practitioner Exam

There are many companies in the globe that are ado... Read More

CSM®️ or PSM™ - Which certificate is more valuable?

IntroductionWhat is Scrum?The source of a correct definition of Scrum is the official Scrum Guide, authored and maintained by Jeff Sutherland and Ken Schaber. Scrum has its roots in software development, but nowadays Scrum is applied in several contexts and industries.From the Scrum Guide:“Scrum is a framework for developing, delivering, and sustaining complex products. Scrum is not a process, technique, or definitive method. Rather, it is a framework within which you can employ various processes and techniques. Scrum makes clear the relative efficacy of your product management and work techniques so that you can continuously improve the product, the team, and the working environment."The latest update to the Scrum Guide also lists possible uses for Scrum:- Research and identify viable markets, technologies, and product capabilities;- Develop products and enhancements;- Release products and enhancements, as frequently as many times per day;- Develop and sustain Cloud (online, secure, on-demand) and other operational environments for product use; and,- Sustain and renew products.Origin of ScrumScrum is a process framework that has been used to manage work on complex products since the early 1990s. Ken Schwaber and Jeff Sutherland worked on Scrum until 1995, when they co-presented Scrum at the OOPSLA Conference in 1995. This presentation essentially documented the learning that Ken and Jeff gained over the previous few years, and made public the first formal definition of Scrum.The Scrum Guide documents Scrum as developed, evolved, and sustained for 20-plus years by Jeff Sutherland and Ken Schwaber.  Both, Jeff Sutherland and Ken Schwaber were present at the event when the Agile Manifesto was written.Scrum was one of the several lightweight processes presented at that gathering in 2001. The Scrum Alliance - a non-profit organization promoting Scrum, was also founded in 2009.Throughout the years Scrum has evolved, and in fact, has been become simpler, but therefore not more easy to apply and practice. In case you're interested, you can look at the Scrum Guide revision history, and see the changes since 2010. To me personally, the beauty of Scrum lays in its simpleness, although some people would advocate they still find Scrum too complicated in terms of process.Scrum Alliance vs Scrum.orgIn 2001, Ken Schwaber left the Scrum Alliance and found Scrum.org. There was a bad impression of the Scrum Master about implementing a Scrum in the organization. The Scrum Masters misinterpreted that the 2-day Scrum Alliance CSM®️ certification course is enough to certify them as a Scrum Master.  Even organizations took amiss that those who attended 2-day training are the Scrum experts.The PSM™  certification of Scrum.org is different than CSM®️ certification. For PSM™ certification, attending a workshop is not mandatory. But, it is little harder to clear the PSM™  assessments which at least assures a precise level Scrum understanding. Note: The Scrum.org assessments are based on the Scrum Guide (fabricated by Ken Schwaber and Jeff Sutherland).Let’s see these two certifying bodies in details and figure out the difference between the Scrum Alliance and Scrum.org.Scrum Alliance- The CSM®️ certifying BodyFounded in 2001, Scrum Alliance® is the largest membership and certification organization in the Agile community. The Scrum Alliance is a non-profit organization and is governed by the Board of Directors. The Scrum Alliance has certified more than 750,000 practitioners worldwide, clearly contributing a lot to the spreading of Scrum worldwide. But, the Scrum Alliance is not simply a company providing training. The Scrum Alliance also organizes twice a year a global gathering and several regional gatherings and supports agile community events.From the Scrum Alliance website:"Scrum Alliance’s vision is to “Transform the World of Work” with a mission to guide and inspire individuals, leaders, and organizations with practices, principles, and values that create workplaces that are joyful, prosperous, and sustainable."Scrum Alliance certificationsAs there are 3 roles in Scrum, the Scrum Alliance offers 3 entry-level (foundational) certifications - there are CSM®️ (Certified Scrum Master), CSPO (Certified Scrum Product Owner), and CSD (Certified Scrum Developer). Next, you could apply for a Certified Scrum Professional (CSP), after indicating your practical experience with Scrum.Recently, the Scrum Alliance has changed the certification path and added an "advanced" certification and course. Today, the Certified Scrum Professional is specific for either Scrum Master, Product Owner, or Developer.These are the certifications:- Certified Scrum Master: CSM®️ --> Advanced CSM®️ --> CSP-SM- Certified Scrum Product Owner CSPO --> Advanced CSPO --> CSP-PO- Certified Scrum Developer (CSD)Next, you can obtain so-called "elevated" certifications, which involves a more rigorous screening and test to validate your knowledge, experience.The elevated certifications target to be an accredited trainer or coach:- CST (Certified Scrum Trainer) - people with this certification can provide official training in Scrum, on behalf of the Scrum Alliance. Trainers go through a rigorous process of co-training, and an application in order to pass the bar of becoming a CST.- CTC (Certified Team Coach) - to be recognized and accredited as a coach on the team level- CEC (Certified Enterprise Coach) - to be recognized and accredited as a coach on the enterprise levelThe coaching certifications involve more than Scrum, but agile & lean coaching in general.The Scrum Alliance also provides an Agile Leadership track - this is relatively new and split into two levels:- Certified Agile Leadership I- Certified Agile Leadership IIThe Agile Leadership courses increase your leadership effectiveness and learn how to be a better leader, no matter what your role.The Scrum Alliance provides also "extended" continuing education, courses.The Scrum Alliance is taking a broad view of how to transform the world of work (e.g. also applications of Scrum outside IT).Scrum.org- The PSM™  certifying BodyIn 2002, Ken Schwaber with others founded the Scrum Alliance and set up the Certified Scrum accreditation series.  Ken Schwaber left the Scrum Alliance in late 2009 and founded Scrum.org which oversees the parallel Professional Scrum accreditation series.On the Scrum.org website, there's a page called "Why Scrum.org?" explaining Ken Schwaber's motivation to separate from the Scrum Alliance and found Scrum.org. These are the motivations as formulated by Ken Schwaber:- I would create a new organization, Scrum.org, to continue developing and sustaining the Scrum Developer program.The program would lead to assessments and certifications based on a body of knowledge.- I would also redevelop a new, more advanced version of the Scrum courseware. This courseware, called Scrum-In-Depth, would focus on how to use Scrum in advanced circumstances. I would publish the Scrum body of knowledge on Scrum.org and formulate beginner, intermediate, and advanced assessments and certifications based on this body of knowledge.- I would form a new group of Scrum Trainers who welcomed openness and transparency.Scrum.org  aims to improve the Profession of Software Delivery and targets its courses and certifications in that area. The Scrum Alliance focuses on Scrum, and takes a broader view, as the Scrum Alliance's slogan is to "transform the world of work".Scrum.org certificationsThe certifications provided by Scrum.org are similar to the certifications of the Scrum Alliance. The certifications are called "Professional" The certification path is as following:- Professional Scrum Master: PSM™  level I --> level II --> level III- Professional Scrum Product Owner: PSPO- Professional Scrum Developer: PSD- Scaled Professional Scrum (SPS), based upon Scrum.org Nexus framework for scaling Scrum- Professional Scrum with Kanban (PSK I): to validate knowledge of how Scrum Teams can use Scrum with Kanban ability to support value creation and delivery. Kanban is a lean method to streamline work. Scrum has its foundations in lean, so it does make a lot of sense for teams to learn and apply Kanban. In fact, agile & lean are blending philosophies.- Professional Agile Leadership (PAL-I): Agile Leadership trackThere’s an optional (non-mandatory) PAL-E (Professional Agile Leadership - Essentials). The workshop provides a foundation for the role that leaders play in creating the conditions for a successful agile transformation.In summary,In a comparison to Scrum Alliance, remember the following practical points when you consider one or the other certification:Scrum.org certifications have no expiration date.Scrum.org certifications can be obtained by taking an online test. Physically attending a classroom course is not required.Scrum.org offers “open assessments” which are interesting for anyone to validate your Scrum knowledge, regardless of if you intend to get certified or not.To know more about various Agile and Scrum certifications and paths to learning these certifications to make a career move, you can refer certification pathway.Choosing between the best Scrum Master Certifications: CSM®️ vs PSM™Agile and Scrum are today’s latest trends. Not only IT-based organizations but also non-IT organizations hire individuals who know the concepts of Scrum framework and its applications. Scrum is the Agile framework, focuses on the complex projects.Initially, the Scrum framework was used for software development, but today it is used as any other projects to get the fastest results. So, there is a rising demand for Agile-Scrum professionals in the organizations.CSM®️ and PSM™  are two major Scrum Master certifications. CSM®️ stands for Certified Scrum Master. CSM®️ is a certification issued by the Scrum Alliance. CSM®️ is a first (entry-level) certification for the Scrum Master. PSM™  stands for Professional Scrum Master. PSM™  is a certification issued by Scrum.org. PSM™  and PSM™  both are the entry-level certifications for the Scrum Master.    PSM™  by Scrum.org has a different approach than CSM®️ by Scrum Alliance in the following ways:- According to Scrum.org, there's no need to attend a class, to be able to take an online test to get certified. A practice assessment is available online, called "Scrum Open"- According to Scrum.org, a certification is a proof of knowledge and therefore has no certification dateLet’s see the differences between the CSM®️ and PSM™  in the tabular form.Certified Scrum Master (CSM®️)FeaturesProfessional Scrum Master (PSM™)50 multiple-choice questions, usually with four possible answersExam Pattern- Number of Questions: 80- Format: Multiple Choice, Multiple Answer and True/FalsePassing score: minimum 69%Passing gradePassing score: minimum 85%- The test is taken anytime after attending the course- There's no time limitExam durationTime limit: 60 minutesEvery 2 yearsCertification renewal durationNo expiration (Lifetime certification)Fee: $1295 per attemptCertification costFee: $150 per attemptThere's no practice exam available. In general, after attending and learning during a two-day CSM course, you should be able to pass the exam without issues.Level of the examDifficulty: Intermediate$119,040  per yearSalary$100,500 per yearFinal ThoughtA search on “Scrum Master”, in the job title with as prerequisite “Certified Scrum Master” gives more than 1000 jobs results. If you want to get an idea what companies and organizations ask in terms of Certified Scrum Master Course, you can have a look at the AgileCareers website (by Scrum Alliance). (there are mainly USA based jobs listed)This is all about the comparison between the CSM®️ and PSM™  and various certifying bodies like Scrum Alliance and Scrum.org that offer these certifications.In the end, knowledge matters whether it is CSM®️ or PSM™  certification. Both certificates have the same value in the job market. Also, both the programs are highly compatible. It is very crucial what you earned during the certification process and the trainer will definitely help you to make the difference there.
Rated 4.0/5 based on 19 customer reviews
5096
CSM®️ or PSM™ - Which certificate is more val...

IntroductionWhat is Scrum?The source of a correct ... Read More