Step by step guide for Problem Solving Workshop
 

The SAFe recommends 6 steps to manage problem solving workshop

1. Agree on the Problem(s) to Solve

“A problem well stated is a problem half solved” 

  • Define problem statement clearly. It shouldn’t suggest solution
  • The team should focus on the problem which they can control or influence
  • The highest weightage should be economic impact. This would inspire team to put in best possible effort to fix it
  • Focus on few and pick the most important one or max two

Tip – You should be looking at ‘What’, ‘Where’, ‘When’, ‘Impact’ but not ‘Who’. The ‘Who’ would result in blame game which is not the intention

2. Perform Root Cause Analysis

By repeating why five times, the nature of the problem, as well as its solution, becomes clear. – Taiichi Ohno 

  • SAFe preloads main bones with 5 categories people, process, environment, program and tools but this can be anything.
  • The team brainstorm the causes and write them against each bone. Brainstorm potential causes before putting things up on the fishbone
  • Apply 5 Whys technique for each of the root cause

Example

Why? – The battery is dead. (First why)

Why? – The alternator is not functioning. (Second why)

Why? – The alternator belt has broken. (Third why)

Why? – The alternator belt was well beyond its useful service life and not replaced. (Fourth why)

Why? – The vehicle was not maintained according to the recommended service schedule. (Fifth why, a root cause)

Tip – The problem-solving teams should attempt to get at least one problem statement under at least three of the five bones

3. Identify the biggest root cause by using Pareto Analysis

    • The teams will use a Pareto Analysis to find 20% of the root causes that caused 80% of the problem.
    • Team members vote on all the root causes which came up during step 2 to identify the most significant root cause.

4. Restate the new problem for the biggest root-cause

    • The original problem statement may no longer be a core issue. Instead it’s the root cause which led to the original problem statement
    • The next step is to pick the cause with the most votes and restate it clearly as a problem. Precisely,
      redefine the problem statement keeping the root cause in the mind (Highest votes)

5. Brainstorm solutions

    • The team members will brainstorm solutions for the newer problem statement with root cause
    • The team brainstorms as many possible corrective actions as they can think of within a fixed time box (about 15–30 minutes)

6. Create Improvement Backlog Items

      • The teams would rank top 3 most likely solutions and out of which they will create improvement backlogs which would be fed to upcoming PI
      • If you don’t take the action on the problem in upcoming PI, the team will lose confidence on the entire effort
Should I go for SAFe SPC Certification (Tips for scoring high in exam)
 

Below are most frequently asked questions from tons of people/SAFe aspirant every month around SAFe SPC CERTIFICATION?

  1. I have good exposure to Agile. In order to boost my career should I go for SAFe SPC certification?
  2. It costs a lot and further $800 to be paid every year to renew it. Is it going to be worth?
  3. How am going to utilize if my company is not on SAFe?
  4. Is it easy?
  5. What’s the process to start teaching? How do I become a trainer?
  6. I am not at all technical and moreover don’t have much exposure to corporate world. What should I do?

Above all, the most important question is

Who is the best trainer? And where should I go and attend the training? 

Let me start with the most important and most frequently asked question. You (or your company) re going to spend good amount of money hence you just want to ensure that you truly learn the concepts so that you can leverage.  I have personally seen many SPCs struggling to teach because they did clear the exam but didn’t understand the concepts well.  People pay the money to be on top in google search doesn’t always mean they are the best. Hence you should do though research before you go for your training. Trust me, the training what you are going to go through has higher weightage than anything else.

I have done good research and I can certainly suggest you the best trainers what I feel would make a difference in your learning based on your location. You can always send an email to me at srsagilechamps@gmail.com and I will guide you multiple options.

The SAFe exam is not easy as well whilst there are two ways you can crack

  1. Be a smart candidate – Find the right trainer, understand the concepts well and further find a right mentor (Many a times your training org/trainer would play that role)
  2. Be a hardworking candidate – You can’t avoid hard work but not focusing no training and just doing everything by yourself. The disadvantage is you may pass but mostly wont score high. Another limitation is you may lose confidence while teaching people.

I always suggest people to pick the first choice. Your hard-work should be to make your future and not just to clear the exam.

If you are not technical at all and don’t know how corporate world works, then I would say go for Leading SAFe instead of picking SAFe SPC. Or probably you can read details over internet or talk to people those who are SPCs and connected to real world problems solved by SAFe. You may find many institutes would lure you with job success etc but without the basics, it won’t add lots of value.

The majority of companies are building their own SPCs hence don’t expect lots of training requests are coming outside of the market. Although in past two years, SAFe has got lots of traction and probably they are the best when you talk about scaling Agile. If you have good exposure to Agile and feel that you are a good trainer, you can attempt SAFe SPC. The SAFe first principle says “Take an economic view”. I think that’s something you should do it as well.

You should always remember, the principle of product management flow – “While you ignore the economics, it won’t ignore you”.

The exam isn’t easy. In fact, I have seen many people failing the exam despite they scored 80 plus marks in Pre Test. Hence do not take it lightly.

You can always refer my other blog which talks about tips and tricks to score high

How do you pass SAFe SPC Certification with high score (Implementing SAFE) – Download questions for free

In order to start teaching within your company, you should complete respective enablement certifications. For instance you want to teach “Leading SAFe”, you should clear the exam for Leading SAFe post SPC.

The Scale Agile is very good in responding any of the queries hence for any specific questions you can send a message to them and you can expect prompt response. I’m personally a big fan of SAFe since it’s not just processes but it does have lots of leadership, and technology.

Another important point to note is that, if you are a good at technology and at the same time you got a good passion towards Agile, you could be a good trainer. The technology knowledge helps significantly if you truly want to be a trainer. Precisely the chances of success and ROI for doing SPC are quite high.

If your company is not using SAFe and you cant do training outside due to the restriction from your company, you should join SAFe forum and start learning more. With my experience I have seen many SPCs were out of SAFe in this situation due to limited exposure and further who would pay $800 renewal every year.

To be honest, this is just high level. The decision depends on many factors. You can feel free to drop an email along with your number. I would try to help you as much as I can. I am usually available for a call over weekend.

Thanks for reading the blog. Wish you happy and SAFe journey.

 

How to pass Leading SAFe or SAFe agilist
 

 

The SAFe (scaled agile framework) is getting lots of attention these days. Everyone is going for various certifications based on the role they are playing in the org. People aspire to get good job are opting for SAFe training and certification as well.

I get tons of questions from students, employees, trainers and career aspirants around how do they pass SAFe certification exam and what’s the way to get the maximum value out of it?

I would focus on various SAFe certifications and who should do in my next blog whilst I would focus on “Leading SAFe” or “SAFe Agilist” in this blog.

The Leading SAFe certification should be done by all the leaders and people aspire to play the leadership. I feel SAFe has lots of leadership content in addition to process and practices. I am sure what you learn post Leading SAFe would be must more powerful than many of the Leadership sessions to attend outside market. The leading SAFe focuses on basic building blocks of SAFe and how does leadership support in doing all the right things. Here are some points you must remember

  1. There are no shortcuts hence if you are thinking you would just pass the exam and you would get all the value, forget about it. The real value is in the knowledge you gain hence choose your trainer (SPC) wisely. Don’t go and pick any trainer. Although passing exam is an important activity since that makes you to force yourself and revise all the concepts.
  2. I would advise you to go with a trainer who has good technical background. In the midst for market value, many professional has become SPC certified. I have attended some of the sessions from non-technical trainers and I can tell you, they could not relate a lots of concepts to what we do day to day. Choosing competent, technical trainer is the half battle won.  A good coach, and if you know basics of Agile, a 3 days – 6-8 hours study can help you to score 90% plus. It may slightly differ based on how fast or slow learner you are.
  3. Once you are done with coaching, you should study the concepts in 1-2 weeks and go for a practice test. If your score is 85 plus, you can review the deck and go for the exam.
  4. All the students must review the Study PDF received from the SAFe (or Download from SAFe website post enrollment), at least three times. There is another slide which talks about specific links (Chapter Wise), which every student must go through at least twice.
  5. It’s good idea to write down the example given by trainer on each slide which would help you to revise the concepts
  6. Aim to score at least 90 percent, not to show people but ensuring that you truly understood each concept.
  7. You should attempt to do at least 400 to 500 sample quality questions to ensure you understood the concepts and you should be able to go for the exam
  8. Never search questions and answers over internet. A lots of answers are correct on internet and moreover it doesn’t give you a feeling that you are attempting an exam
  9. There is going to be approx. 10% repeat questions from pretest hence do ensure that you got answers for all the pretest questions

I am going to start community of practice on telegram. In case if anyone is willing to join to find

Who is the best trainer in your area?
Which certification I should opt for?
Should I do SPC certification and become trainer? What’s the step by step process to do that?
Any other question pertaining to SAFe?

You can click on the click below and join SAFe community of practice
https://t.me/joinchat/GVqVCQbIO5QK5JqB

 

The sample questions from scale agile are

1. What is the connection between feedback and optimum batch size?
A. Lack of feedback contributes to higher holding cost
B. Feedback and batch size are generally not connected
C. Small batch sizes enable faster feedback with lower transaction costs
D. Large batches reduce transaction cost and provide a higher return on investment
2. What is one key reason for keeping the test data for automated tests under version control?
A. For reporting and auditing purposes
B. Version control is required for quality standards
C. All enterprise assets must be under version control
D. If test data gets out of sync, automated tests may not properly execute
3. What is the primary goal of decentralized decision-making?
A. Reduce Cost of Delay
B. Resolve dependencies
C. Enable faster flow of value
D. Increase alignment
4. What does SAFe® Principle #3, “Assume variability; preserve options,” enable?
A. Better economic results
B. Specification traceability
C. Up front design of systems
D. Stronger Definition of Done
5. What is a result of shorter queue lengths?
A. Lower quality
B. Increased risk
C. Less variability
D. Longer cycle times
6. Which statement is most accurate about the Program Vision?
A. It expresses the strategic intent of the Program
B. It drives the allocation of budget for the Agile Release Train
C. It summarizes the team PI Objectives for the current Program Increment
D. It provides an outline of the Features for the next three Program Increments

7. What Definition of Done is required for the Iteration Review?
A. Release
B. Team Increment
C. System Increment
D. Solution Increment
8. What is the primary purpose of Strategic Themes?
A. Determine the order in which Epics should be executed
B. Drive incremental implementation across the enterprise
C. Connect the portfolio to the enterprise business strategy
D. Define the sequence of steps used to deliver value to the customer
9. An Epic spanning two PIs was approved for implementation. What is the optimum implementation path from a Lean-Agile perspective?
A. Implement the Epic across the same number of PIs as it took to develop
B. Report the percentage completed to the key stakeholders at every PI boundary
C. Demonstrate the progress to the key stakeholders after two PIs and have them accept the epic
D. Demonstrate the progress to key stakeholders after first PI and make a decision how to proceed
with the Epic in the second PI
10. What backlog items are part of the Solution Backlog?
A. Benefits
B. Features
C. Capabilities
D. User Stories

Answer Key:
1. C
2. D
3. C
4. A
5. C
6. A
7. B
8. C
9. D
10. C

The understanding of below concepts would help you to score high

  1. What is business Agility?
  2. What are 8 Kotter’s Principles?
  3. What is the benefit of Decentralize decision making? Delivering value in shortest sustainable lead time, better control, high morale, empowerment
  4. What is MVP? Minimal Viable Product which can prove benefit hypothesis
  5. Who has the content authority on Team Backlog or Program Backlog or Solution Backlog? Product Owner, Product Manger and Solution Manger Respectively
  6. What are two ART sync meetings? SOS and PO Sync
  7. House of Lean
    • What is the most important item? Value
    • What is the foundation of House of lean? Leadership
    • What are the four pillars of house of lean? Respect for people and culture, Flow, Innovation, Lean, Relentless Improvement
  8. Which of the core competencies of the Lean Enterprise helps align strategy and execution? – LPM
  9. What are types of  Guardrails – BO Engagement, Horizons, Capacity allocation, approve EPIC initiatives
  10. What are core values of SAFe – Transparency, Program Execution,  Built in quality, Alignment
  11. How do you achieve Cadence based synchronization in SAFe? PI Planning
  12. Who Facilitates ART – RTE, Who Facilitates Solution Train – STE
  13. What decisions you shouldn’t centralized?  Decisions with big economic impact and which are not likely to change
  14. ROAM full form – Resolved, Owned, Accepted, and Mitigated
  15. CALMR full form – Culture, Automation, Lean Flow, Measurement, and Recovery

 

 

Should I start thinking about switching from Scrum to Kanban?
 

I want to release anytime, I don’t want iterations, I want to skip estimation, I have challenges with self-organizing teams, I want to change my priorities,

I need better visualization, I want to process that is more adaptable, Scope creep is my major concern, I am want to handle support tickets,  I am afraid of sprint failure and end of picking less work, I can’t break down stories enough to complete within the sprint.

Before I get into details, review below carefully, this would suffice the need for moving to Kanban over Scrum or XP.

  1. There are teams that have a more responsive nature of work like maintenance, fixing customer bugs, run time day to day requests, etc.
  2. It may not be a good idea for these teams to plan the sprint or iteration since a lot of activities will become overhead. In addition to that, we need to break the Agile principles for instance constantly adding items to sprint during execution, not doing refinement in advance, accepting back-to-back sprint failure, and more.
  3. Not doing Scrum does not mean they would not publish the work. They are still expected to commit approx work (Preferably in terms of story points) in a given time period.
  4. They commit to goals and SLA based on the past data

Scrum is great while the world is not a perfect place. You can always overcome challenges associated with it but if you have another Agile method is even more flexible there is no harm in leveraging that. I see many organizations are switching to Kanban and getting wonderful results. I don’t have the intention to move you from what you have been doing while I am just trying to initiate a thought process and philosophy around Kanban.

Let’s understand the above in more detail with real-time scenarios. A group of project managers gathered to discuss the challenges they have with the existing process with senior management.  Let’s look at some of the interesting areas what they have put forward on the table (I am sure you can relate one or more areas if you have managed agile teams)

 

Project Manager 1: (Team is afraid of Sprint failure) My team has very fewer items in sprint compare to what they can accomplish as they are scared of sprint failure.  Despite that, I don’t have successful sprints as one or items roll most times as we get blocked. I can’t allow my team to pick more middle of a sprint

Project Manager 2: (Prod issues; Lot of support to other teams) My team builds new features while I am expected to support some of the other teams for whom we provide back-end services. The requests coming from them is our top priority whenever it’s related to prod for them.  The amount of work that comes from different teams vary and we cannot assign fixed bandwidth to deal with those issues. Most of our Sprint we have one of these two situations

  • The sprint fails because we need to focus on supporting other teams.
  • We are done much before the sprint ends.  Pulling new work is not allowed mid-sprint hence we use that time for learning while this is not a great idea all the time.

Project Manager 3: (Support work; Tickets) I have all the support work. The estimation has been a challenge most times. A bug takes a day or a week, it all depends on the product I work for is huge and we have most of the newer members.  How can I make sure my sprints are successful and at the same time, we as a team don’t under commit?

Project Manager 4:  (Adaptive to more adaptive) My team hates too many ceremonies and processes. They think of having a lightweight process which is more adaptive over-prescriptive,  is much better. All of them are experienced/committed and understand their roles and responsibilities.

Project Manager 5: (Time and material; Longer stories; Unpredictable work) We built adapters and I don’t see the benefit of breaking down and doing that in parts. We have a deadline for every adapter and we kept getting blocked. We are fine to wait as we are on the “time and material” contract. Getting blocked from the customer end doesn’t harm as billing doesn’t stop.  How do I fit in a work which takes a few weeks to a couple of months?

Project Manager 6: (Frequent priority shiftOur priorities changes very frequently.  Many times we literally have to stop what we are working on and start something else. Getting new work done in the next sprint doesn’t help as the work we are doing becomes useless even if that’s completed due to change in priority.

Project Manager 7:  (Customer or Sprint successOur company’s top priority is to manage customers and their expectations while we always focus on velocity and sprint success. This becomes challenging as in order to manage customer priorities, we compromise Scrum priorities or vice versa. Both are not good ideas. In the first option, you are disregarding a process resulting in low team morale and an unpredictable outcome.  The later is not acceptable anyway 🙂

Project Manager 8: (The product owner struggles) The PO struggles to lock down the requirements for a week. He keeps adding work to sprint throughout the week, changing existing requirements, and even providing/updating acceptance criteria during the sprint.

Projects Manager 9: (Team experience or complex work) My team has challenges with breaking the requirements or estimating the work.  The sprint success matters most to me (Why-Sprint-Success-is-Important). I end up being unhappy most times.

Kanban could be one of the solutions for most of the problems listed above. The comparison of Kanban with Scrum/XP and some of the core frameworks is available here

Sprint success is really important when you talk about Scrum. The Sprint fails due to a variety of reasons like team experience, The challenges with breaking down stories, unpredictable work, Customer focus precedes team priorities, support work, and many other challenges as listed above. Many times either we run too much to having a successful sprint (By means of slogging or patch up work) or do not think of a successful sprint at all. Both are not good options.

In my upcoming blogs, I would be talking in detail about how to use Kanban, best practices, myths, and an easy shift from the existing process to Kanban. Please provide your comments below. This would help me to cover all aspects of my next set of blogs on Kanban.

 

 

 

Why do people say SAFe is a top-down command and control approach
 

 

SAFe Agile is extremely prescriptive, works only with command and control from the top management – Is this a Myth?  – Let’s explore to know the answer

is SAfe safe

Before I share my thoughts, let me add a disclaimer

  • I have a strong faith in SAFe
  • I am very much inclined to SAFe values, principles, and practices

“If you are on agile, scaling agile becomes relatively easy”

Let’s say your company is running on broken agile processes or is on a waterfall methodology, you can still be successful with SAFe but the chances are reduced significantly.   The SAFe suggests significant benefits in 3-5 years while you will hear from people that the magical outcome in productivity, quality, employee morale, etc would come in 3-6 months.  Let’s explore slightly deeper:-

I think you would agree that most of the transformations begin with top-down command and control for the simple reason that change is not easy and it needs a real push if it’s not small.  This would shift unorganized functions to be more organized, pushes people hard for delivery, teams start running on cadence and synchronization if it’s SAFe resulting in higher productivity, quality and so is the outcome.  The KPIs, Metrics, and rigid processes make people do more. There is a forced innovation in the beginning as well. But remember that this would not go long run. The management started believing that we have showcased better outcomes hence let’s not stop. They go with 100 percent utilization which is a disaster (SAFe says so, and I completely agree).  The fall begins within 1 or 2 years and it becomes very tough to manage it.  The command and control is fine at the start but it should be strictly looked into in six months to a year. The management needs to focus on generative culture, autonomy, and decentralized decision making.

We need to have a relentless improvement in not just the outcome but employee well-being, morale, and learning. We should ensure that we stick to SAFe values and principles.  One of the main reasons I have seen for SAFe failure is organizations do not invest much after little success or Org is not ready to move to SAFe but they want to be part of the rat race.

People talk about only success stories while there is a good number of failure stories as well which probably is not taught anywhere. I met many people who ask the interviewer whether the company they are giving an interview is on SAFe or planning to adopt in near future. If the answer is yes to any of these two questions, they don’t want to join the company. There is a myth and perception created while that doesn’t seem to be true. The management truly has to involved at ground level in order to break the myth and move their towards the real benefits of SAFe.

We should all remember that identification of value streams and ARTs, Identification of EPICs are core challenges while implementing SAFe while organization alignment still remains the priority.

Scrum vs Extreme Programming (XP)
 

Scrum vs XP

Both are very similar that are aligned with each other and complement each other.  If you walked to a team then it very is very hard to recognize which practice team is using if they are using one of the above practices.  XP is Scrum with technical practices. It’s mindset/behavior and a more prescriptive approach with a strong feedback loop.

Scrum
XP
The iteration is between 2 to 4 weeks. The iterations are 1-2 weeks or less. For very aggressive teams, it can go up to a day.
In Scrum product owner prioritizes the product backlog but the Scrum team has a privilege to chose a lower priority item in a sprint to work on before the high priority XP teams must always work in priority order as features to be developed are prioritized by the customer.
Changes in the sprint are not allowed XP Teams are much more amenable to change within their iterations, but change can only be made if the team hasn’t started working on a feature and at the same time the change is of the equivalent of the swapped item.
The validation of the software is completed almost at the end of each sprint, (i.e. Sprint Review) The software needs to be validated at all times, to the extent that the tests are written prior to the actual software.
Scrum doesn’t prescribe any engineering practices The XP does.
The Scrum Master is responsible for what is done in the Sprint, including the code that is written A developer can modify or refactor the parts of the code as and when the need arises.

 

The teams start with Scrum and move towards XP. There is lots of focus on Self Organizing teams and XP encourages that to a great extent. The Maturity model that we have prepared for CDK has more focus on Scrum up to level 3 and further, the direction is to adopt XP in order to get on to level 4 and 5.

The original XP is based on four simple values – simplicity, communication, feedback, and courage – and twelve supporting practices as listed below

The Planning Process

The desired features of the software, which are communicated by the customer, are combined with cost estimates provided by the programmers to determine what the most important factors of the software are. This stage is sometimes called the Planning Game.

Small Releases

The software is developed in small stages that are updated frequently, typically every two weeks.

Metaphor

All members on an XP team use common names and descriptions to guide development and communicate on common terms.

Simple Design

The software should include only the code that is necessary to achieve the desired results communicated by the customer at each stage in the process. The emphasis is not on building for future versions of the product.

Test-Driven Development

Testing is done consistently throughout the process. Programmers design the tests first and then write the software to fulfill the requirements of the test. The customer also provides acceptance tests at each stage to ensure the desired results are achieved.

Refactoring

XP programmers improve the design of the software through every stage of development instead of waiting until the end of the development and going back to correct flaws.

Pair Programming

All code is written by a pair of programmers working at the same machine.

Collective Ownership

Every line of code belongs to every programmer working on the project, so there are no issues of proprietary authorship to slow the project down. The code is changed when it needs to be changed without delay.

Continuous Integration

The XP team integrates and builds the software system multiple times per day to keep all the programmers at the same stage of the development process at once.

40-Hour Week

The XP team does not work excessive overtime to ensure that the team remains well-rested, alert, and effective.

On-Site Customer

The XP project is directed by the customer who is available all the time to answer questions, set priorities, and determine the requirements of the project.

Coding Standard

The programmers all write code in the same way. This allows them to work in pairs and to share ownership of the code.

How do you pass SAFe SPC Certification with high score (Implementing SAFE) – Download questions for free
 
SPC 5.0

SPC 5.0

The SPC is a SAFe program consultant (Also called as Implementing SAFe). This is probably the highest level of certification SAFe has and undoubtedly highly valued in the software industry.  I am fortunate to have it cracked within 3 days of effort plus 4 days of a class. I definitely would like to write this down so that it would become easy and you don’t need to wonder how would I go about not just passing but scoring high marks.

I feel you should first decide whether you truly want to do it. If you just want to add another certification to your profile, probably I would say you don’t need to go for it.  If you aspire to be an Agile coach and/or know that you would be implementing/supporting SAFe then it’s the perfect thing to go for.

I have cleared a SAFe Program Consultant a couple of weeks ago.  I am going to share tips that would focus more on learning but at the same time, you will clear the exam with an excellent score.

  1. Read the material given by SAFe at least two times. If any concept is not clear then refer to scaleagileframework.com. The explanation there is far better than any other place.
  2. Click on the big picture and understand every item. The better way to do is to click on the item and read about it.
  3. The specific links are given in exam preparation material, read them all at least twice. Create notes only for high-level titles that would help you to connect with questions.
  4. The practice test must be done and if you score less than 80% then you need more preparation.
  5. The exam guide clearly states the most important chapters. The way you determine is based on the number of questions that appear from the respective chapter. Anything above 10% is very imp and every concept should be understood well.
  6. If you need any guidance in terms of how to prepare for exam, you can send an email to me at srsagilechamps@gmail.com . There are no sort cuts but right preparation will yield excellent results. Alternatively if you are on whats app, you can join my group to participate in SAFe discussions                                       https://chat.whatsapp.com/IsMoFcc7znF4y5Y8s131LX
  7. Avoid searching for answers to questions on the internet during the exam.  You may find the question while the answer available on the internet may be wrong.  Study well and go by what you think is right. The questions are prepared with very well thought processes and I am sure you should be able to answer. If you want to score high, trust your judgment. Remember certification doesn’t have lots of value while knowledge does. 
  8. The questions that I found on the internet are

9. I would recommend reading Get SAFe Now book before even you go for training or start reading materials from SAFe.   The book is for beginners and explains the concepts in layman language. The questions after every topic make you think a little deeper.  It helped me a lot to hit high scores in a bunch of certifications I did.

The above is just for basics while if you want to be really confident then I would recommend reading the below book (SAFe distilled 5.0) instead of going through the website and reading random links. This book is organized so well that everything seems to be a story.

I will be adding more blogs with cheat sheets and more informative ideas and content soon

The sample questions available on the internet may help you to prepare further

 

 

Agile Myths
 

Myth 1. Stand-up is a status meeting
Reality – The Daily standup is a Planning Meeting. It promotes Collaboration, Self-Organization, Enables inspection and Adaptation, Focus on achieving the outcome.

Myth 2. Pair programming decreases the productivity
Reality – The pair programming increases the productivity in majority of the cases if done in right way.

Myth 3. Agile doesn’t need project manager
Reality – The Scrum Master plays a role of a project manager.

Myth 4. Agile is another word for Scrum.
Reality – The Scrum is one of the Agile framework. There are many more like Kanban, XP, FDD etc.

Myth 5. Agile is faster than Waterfall
Agile is less about delivering software faster, and more about delivering value faster.

Myth 6. Agile means no documentation
Agile doesn’t do documentation for documentation’s sake. Documentation is like any other deliverable on an Agile project. It gets estimated, and prioritized like any other user story.

Myth 7. We’re a self-organizing Agile team, so we can do anything we want
Reality – The core principles are not allowed to be tailored. It is a lightweight process while the core practices are expected to be followed.

Myth 8. Agile is a silver bullet
Reality – The projects done in Agile do fail. It cannot be an excuse to stop thinking. Agile promotes fail faster philosophy so that one can learn from it.

Myth 9. The story points can be exactly translated to hours.
Reality – When the team gets mature, you can translate it to approx but not exact hours.

Myth 10. The product owners, developers and scrum masters get to do what they like.
Reality – The Agile is very disciplined framework. Every role has set of responsibilities. The core responsibilities should not be switched.

Myth 11. There is always a right size for a user story.
Reality – Every team is different hence there is no right size of the user story. The team producing 30 story points can be more productive than the team doing 45 story points.

Myth 12. Agile means no planning, no design
Reality – Agile typically needs more planning and design than waterfall. Both of these activities happen throughout the development.