News, Analysis, Articles, and Resources for Certification Courses

Latest Posts

Who Is a Cspo? - Roles and Responsibilities

By Frederik Vannieuwenhuyse

1.1 What is a Product Owner?A Product Owner is a role defined in Scrum. Scrum is a framework for complex product development (*). The Product Owner is responsible for maximising the value of the product resulting from the work performed the Development Team. The role exists in Scrum to have 1 person with a clear accountability of WHAT product or service will be built. The Product Owner role is also used as a title outside Scrum, in other frameworks, but if you want to understand the definition of the role and responsibilities of a Product Owner, you need to start to look and to understand it in the scope of a Scrum Team. (*) (“product”, to be defined in context, this is a generic term for the product or service being developed for the end-users)(*) (“development”, also to be defined in context, this is a generic term for all activities needed to create and deliver value to the end-users)1.2 What’s the job profile of a Product Owner?The Product Owner role is Scrum is a role, both with a tactical, strategical and operational aspect. The Product Owner role is critical as the role is kept by 1 person (and 1 person only) for a specific product. Having 1 person holding the role simplifies the accountability in terms of having 1 spokesperson for product ownership and accountability of maximising value. This doesn’t mean that all activities are to be done by the Product Owner; otherwise the Product Owner could become a bottleneck. The Product Owner does remain accountable at all times. To be able to do the job, the Product Owner has business (domain) knowledge, affinity with end-users, affinity with “development” (activities needed to deliver a piece of value), and knowledge of how to do agile product management. Product management is a multi-disciplinary job, and it involves to understand, empathise, quickly inspect & adapt, each time with the accountability to make the right choices in terms of what to built next, in order to continuously (incrementally) deliver value to end-users. In order to better understand what kind of profile is needed to fulfil the product owner role, it’s valuable to list skills required and activities performed.When looking for a Product Owner, you’re looking for a profile with generic product management skills and product-specific skills. The generic skills are needed to be able make decisions on a strategic and tactical level.People skills a Product Owner must have:A Product Owner also needs people skills:To empathise with users of the productTo build connections with stakeholders and to create a healthy working relationship with the team building the product. These people skills include- to be able to listen (to stakeholders, end users, team members), to translate information (between people with a different background), to be able to make informed decisions without undermining longer-term objectives, etc.The product-specific skills are defined by the product or service that’s being built. This includes all the activities to understand the market, the needs, the job the product or service will fulfil, user-journeys, also more technical product-specific knowledge, legislation (if applicable), financial implications and any other constraintIn his book Product Mastery “From Good to Great Product Ownership”, Geoff Watts describes the skills of Product Owners with the acronym “1.3 Product Owner role and responsibilitiesThe role of Product Owner can be quite challenging and high-demanding. When reading The Scrum Guide, it says that product backlog management is the main activity for a Product Owner. The product backlog is a tool to ensure it’s clear what’s needed in the product and what’s the most valuable thing to build next. Managing a backlog, and refining items on the product backlog is a continuous activity. The Product Owner often serves as the spokesperson of the product. This means he/she needs to be able to answers questions appropriately, for example regarding product vision, roadmap, planning, why certain choices have been made, etc. This also includes NOT answering certain questions, because the Product Owner knows the development team is in a more appropriate position to answer the question more accurately, and as well to facilitate a conversation with the development team involved.Go through other roles and responsibilities of Product Owner here.1.4 How does a Product Owner manage various stakeholders desires for the product?The Product Owner has the challenging task to manage requirements and desires of stakeholders. Each stakeholders will certainly advocate his/her demands are the most important. Here are some recommendations on how a Product Owner can deal with this:Treat requirements & desires as “desirements”, meaning, until by learning or by end-user feedback has been proven that the “desirement” is valuable, treat it as a hypothesisKeep the product backlog and its ordening as transparent as possible to all stakeholdersDon’t be seduced to prioritising in categories such as high, medium, low priority. A product backlog is ordered, no two items can have the same priority.Use techniques to prioritise impacts (impact mapping), simulations to learn stakeholders to prioritise (e.g. buy a feature), techniques to slice for value (user story mapping) 1.5 CSPO vs PSPO CSPO is an abbreviation which stands for Certified Scrum Product Owner. This is a certification offered by the Scrum Alliance, specifically for the Product Owner role. PSPO is an abbreviation which stands for Profession Scrum Product Owner. This is a certification offered by scrum.org, specifically for the Product Owner role.In my opinion, both certifications are equivalent and define a high-quality standard. There’s a difference in the way of obtaining certifications and how to maintain this. Certifications issued by Scrum Alliance are obtained by taking an online exam after mandatory attending a 2-day training given by a Certified Scrum Trainer.Certifications issued by scrum.org are obtained by taking an online exam without the prerequisite of attending a training. Certifications issued by scrum.org do not expire. Of course, to test and validate your knowledge, having a decent understanding of the product owner role is mandatory, therefore preparation and study are key. Participating in a training to learn, and to experience what Scrum is about, is always highly recommended.1.6 Product owner in agile software development The manifesto of agile software development does not specify anything about the Product Owner role. Therefore, it’s perfectly possible to have an agile team without a Product Owner.The manifesto for agile software development does state a few principles which illustrate how we want to work regarding product and value delivery, for example:“Our highest priority is to satisfy the customer through early and continuous delivery of valuable software;”“Welcome changing requirements, even late in development;”“Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale;”“Business people and developers must work together daily; ““Working software is the primary measure of progress;”You can interpret these principles as following, in what you should NOT be doing…Waste time & effort creating long-term plans, long cycle times, etc without actually delivery usable product increments to the end-users, …Waste time & effort on unnecessary specifications; unfinished product (“inventory”); or unvalidated requirements (which are assumptions in disguise), …Waste time & effort on unnecessary handovers between business people and development teams, …Waste time & effort on assuming what’s valuable for the end-users, and not verifying this by letting end-users try out working software and based upon their feedback, inspect & adapt, improve the product together, …Wasting time & effort in demanding upfront detailed estimates for unreasonable long periods (e.g. all estimates for the next year…)Wasting time & effort on detailed long-term planning, fixing agreements, treating change as evil, …1.7 Product owner in Scaling AgileLets first make the statement that you need to consider it twice before blindly scaling up any development efforts. In general, we are trying to deliver value by keeping things simple, simplify working processes, and collaborate to maximise effectiveness and customer satisfaction. In case you need to align several development teams to work together on the same product, take the following into account:A product has 1 product owner, this means in case of several teams developing on the same product, there’s 1 product ownerA product is defined as something meaningful and valuable for a customer or end-user, not a technical componentA product has 1 product backlog, as long the product lives, the product backlog existsA product owner can delegate areas of the product to other product owners, but take care to not have “proxy” product owners, with a mandate to decide. The ‘chief’ product owner remains accountable for overall prioritisation. Some scaling frameworks make a distinction between “product management” and “product ownership”, in any case ensure there’s alignment regarding product management, no conflict in priorities, and no unnecessary handovers of information.1.8 Who is accountable for the business value delivered by a Scrum team?The Product Owner is responsible for maximising the value. A Scrum Team collaborates to deliver value together. The Product Owner remains accountable.1.9 What exactly is the role of the Product Owner during the Daily Scrum?The Product Owner is not required to attend the Daily Scrum. The Daily Scrum is an inspect & adapt time-boxed event for the development and performed by the development. This is defined in this way because otherwise the Daily Scrum will quickly be run as a status meeting (and not a daily planning event). Of course, the Product Owner can be present during the Daily Scrum, as it’s a great moment to check-in with a team, listen how a team is synchronising, ask and answer questions - after the Daily Scrum. The Product Owner, nor the Scrum Master should be leading the Daily Scrum. They can be present, but the Daily Scrum is an activity (‘Scrum’ metaphor of Rugby), for and by the development team. The Product Owner defines a sprint goal (a sprint is a time-boxed iteration to deliver a potentially shippable product increment); the Development Team inspects its progress on a daily basis towards that sprint goal, using the sprint backlog.1.10 What are certain anti-patterns regarding Product Owner?Some example anti-patterns regarding Product Owners; this can be used in an exercise to coach Product Owners. Ask what should be done to be the WORSE Product OwnerIdentify what’s actually being done of that listIdentify what should be STOPPED doing, in order to improveSome anti-patterns of Product Ownership Becoming a bottleneck in communication, so that’s there’s a delay in the flow of value between the development team, end-users, and stakeholders, …Taking decisions in isolation, so that the reason why decisions are taken are not known, nor understood, …Specifying technical solutions, and not articulating the business value, … (technical solutions are the responsibility of a development team)Pressuring the speed of delivery, resulting in less quality and inability to validate if value is being delivered, …Not listening to the product development team’s recommendations, not engaging in any healthy dialogue, …Not articulating the product’s vision, and/or strategy, resulting in development teams functioning as “feature factory”, without investigating what’s valuable and what’s not, …Inadequate product backlog management, resulting in unready items to plan, long inventory, unclear prioritisation, …Not accepting or rejecting work according to the definition of done, resulting in unclear standards of what’s a done product increment, …Not thinking how to delivery slices of value, forcing development teams to deliver components, instead of ready-to-use product increments, …Not facilitating a sprint reviewNot participating in any retrospectiveNot updating any forecast after finishing a sprintNot engaging with end-users / customers to get feedback etc What is the process to get a CSPO certificate?You can also follow the below steps to understand clearly.Find a Certified Scrum Product Owner course on the Scrum Alliance websiteRead and understand the Scrum GuideRead and understand the manifesto for agile software developmentRead and understand the learning objectives of a CSPO courseAttend the 2-day CSPO courseComplete the online CSPO exam, the fee is included in the course price. After completing the course, your Scrum Trainer will upload your user information into the system of Scrum Alliance, next you’ll receive an invite to do the online exam. Recommended books and material to read and further prepare:Articles by Roman Pichler,Book Product Mastery, by Geoff Watts, Path forward after CSPO at Scrum AllianceCertification gives you access to a renewable, two-year membership with Scrum Alliance. As a Certified Scrum Product Owner (CSPO™), you can continue your educational development to become an:Advanced Certified Scrum Product Owner (A-CSPO™)Certified Scrum Professional - Product Owner (CSP-PO™)Certified Team Coach (CTC™)Certified Enterprise Coach (CEC™) Certified Scrum Trainer (CST™)Remember, if you’re starting as Product Owner, the CSPO certification is only the start of your journey!ConclusionBeing a product owner is a satisfying job! You are the main spokesperson for the product. You act as a catalyst between the Development Team and the outside world. You take decisions to maximise product value while taking into account various constraints.

Rated 4.5/5 based on 14 customer reviews

Who Is a Cspo? - Roles and Responsibilities

Blogs

5518

Who Is a Cspo? - Roles and Responsibilities

by Frederik Vannieuwenhuyse
15 Feb 2019
9 mins read

1.1 What is a Product Owner?A Product Owner is a r... Read More

Reap The Benefits Of Your PMP® Certification

By KnowledgeHut Editor

What makes you stand out in the crowd as a PMP® certified professional? PMP® Certification is considered worldwide as the gold standard for project management certification. One needs to do a lot of hard work in order to acquire one, which includes specialized formal training and several thousand hours of practical experience in order to pass a rigorous certification exam.This entire process helps to validate your project management skills as well as, it ensures that you have the knowledge of the highest standard that makes you apt for the role of Project Manager. Once you get PMP® certified, you need to maintain it by earning PDUs, as your PMP® certification is only valid for 3 years. Now, how does all this hard work benefit you?Advantages of being PMP® CertifiedGot PMP® certified? Then it’s time for you to reap the benefits out of your PMP® Certification.PMP® certification is an unbiased endorsement of your professional experience and project management knowledge at a global level. Having this certification under your belt exposes you to benefits like high market value, increased credibility, and most often, a higher pay. But is it worth getting a PMP® certification? This is the most common question that arises in your mind when you prepare yourself for a costly and complicated journey to get PMP® certified. The following benefits will surely help you to find the answer to your quest:Beef up your resume with PMP® CertificationYou can add more value to your profile by adding a PMP® certification to your resume. Employers hiring Project Managers prefer PMP® certified professionals over non-certified professionals.PMP® certification validates your project management experiencePMI (Project Management Institute) has set certain standards in regards to applying for the PMP exam. You need to acquire a certain amount of experience in directing and leading projects. Also, PMI has an audit process to ensure that you are truthful about your project history.Get networking and potential job opportunities as a PMP® certified professional The PMI chapters frequently organise meetings and workshops where project management professionals come together to learn the theories related to project management. These events also help you to earn PDUs which are valuable for renewing your PMP® certification when it expires in three years.These events expose you to discussions regarding fresh career opportunities from members who appreciate the importance of PMP® certification.PMP® certification proves your commitment towards the profession of project managementAs a PMP® certified professional, you spent your effort and time to attain your PMP® certification. This clearly shows your commitment to project management.Enhance your skillsYou need to undergo rigorous training in order to get PMP® certified. This also includes a significant amount of coursework. You get the opportunity to get trained and educated in five project management processes which include initiating, planning, implementing, controlling, and monitoring.To be precise, PMP® certification teaches you each and everything about project management which you can implement in your company for better project execution.Increase your earningYou tend to earn more as a PMP® certified project managers than the non-certified ones. You can increase your salary as a PMP® certified professional and expect an immediate hike as soon as you get PMP® certified. Surveys show that PMP® certified project managers earn 20% more than the non-certified project managers. Further, PMP® certified professionals have the capability to earn a six-figure income. Other benefits There are numerous benefits of PMP® certification apart from the above-mentioned ones. Whatever field you belong to; finance, commerce, telecom, research, business, or technology, a PMP® credential will upskill your project managerial skills and allow you to step to new markets, new industries, and new countries.Although, you might feel demotivated for taking up the lengthy exam process and course fee, your money, time, and effort is worth as it returns you the benefit beyond you can imagine. Should I get a PMP® certification?If you are someone who’s passionate about Project Management and working in the project management field then you should definitely begin your journey for PMP® certification. It is a well renowned and respected certification with an excellent scope. It is mandatory in many organisations for a Project Manager to hold a PMP® or an equivalent certification.Once you are PMP® certified, you begin to progress both in terms of career and salary. According to PMI’s Salary Survey 9th edition, the salary of professionals with PMP® certification is 20% more on average than their non-certified counterparts. You need to fulfill the following requirements to appear for your PMP® certification exam:Project Management Experience (36 months for a 4-year degree holder and 60 months for a high school diploma or equivalent holder)35 hours of Project Management EducationIf you hold a bachelor's degree or global equivalent, then you need to have 4500 hours of Project Management experience.If you hold a high school diploma or global equivalent then you need to have 7500 hours of Project Management experience. Why do employers want you to be PMP® Certified?Requiters looking for project managers divide the resumes into two piles: those with PMP® certification and those without. The following points will help you to understand why a PMP® certified professional is desired by the employers:Demand from customersAccording to Tim Wasserman, Program Director of Stanford’s Advanced Project Management Program, ‘Highly regulated industries (e.g., financial services, pharmaceuticals, defense, and aerospace) wouldn’t consider anyone without the PMP® certification’.If you are working in a company who has bid on a government project then you are likely to encounter a requirement for PMP® certification. But this requirement is not limited to government entities. The business approach for certain types of firms requires adherence to strictly-defined processes for which PMP is a must.PMP ensures your ability to speak the common language As a project manager, you are likely to spend the majority of time communicating with your team members who might differ from project to project. Therefore, your ability to speak the common business language ensures that you are on the same page with your team members, program manager, sponsor, etc.Although you can’t be sure that you will eliminate all kinds of possible miscommunications by having a team full of PMPs, this will surely reduce the chances of such scenarios as the entire team will have the common understanding of what each process and technique seeks to achieve.PMP shows that you can manage projects in a structured and repeatable fashionThe project management experts around the world use a set of repeatable and standardized processes to tackle the value of every unique process. PMI addressed the increased need for standardization of processes in its 2013 Pulse of the Profession™ Study. The tools, processes, and documents endorsed by PMI enable you to confidently and effectively manage the risk in any project. Moreover, you can ensure that the partner organisation and your team members are on the same page in regards to the management approach and risk identification.How does your PMP® certification benefit your employer? Adding a PMP® certification to your profile automatically opens up many beneficial doors for you as well as your employer. PMP® certified professionals are the leaders of some of the world’s top projects in renowned organisations. If you are imagining that how can a PMP® certification benefit your organisation, then these are the various benefits which your organisation can reap out of your PMP® certification:International recognitionAdd value to your companyCreate a healthy business cultureHaving organisational adaptabilityInternational recognitionPMI earned the ISO/IEC 17024 accreditation in the year 2007 for PMP® certification program. Since then, PMP® certification is an internationally recognised qualification which has the credibility in more than 85 countries which have endorsed and adopted ISO standardization practices. This clearly means that it is a certification recognized by the global community for its value and standardize the experience and qualification which a non-certified individual doesn’t hold. Once you get PMP® certified, you become a valuable commodity for your organisation if it intends to have a strong global presence and influence.Add value to your companyOnce you are PMP® certified, you start adding more value and a great benefit to your organisation. You are looked upon as a person who truly knows what he or she is doing.Your PMP® certification proves to be beneficial for your company in the following ways:Your organisation knows that the employees are getting led by someone who has the knowledge and experience to ensure that they work to the best of their ability.As a certified project manager, you have extensive knowledge about risk management and your company is assured that you will avoid any unnecessary mistakes that would lead to monetary loss.Your clients will be assured that they are getting the best service possible.Create a healthy business culture According to PMI, organisations are formulating their visions by integrating project management into it to create a healthy business culture. It further acknowledges that the most effective organisations recognize the need for a formal program and project management in their initiatives to change the business. The following factors play a pivotal role in an organisation while creating a culture that embraces project management and increases the business value:Understand the value of project managementActive engagement with executive sponsors on programs and projectsGetting projects and programs aligned with the organisation’s strategyHaving a highly matured program, project, and portfolio managementHave organisational adaptabilityPMI’s research shows that the skills demonstrated by PMP® certified project manager contribute towards the preparedness of a business or company for the market and environment change.ConclusionAs we have discussed all the benefits that your PMP® certification can bring to you and your organisation, we can sum it up as; PMP® certification improves your opportunities and skill set at the individual level and helps to manage the challenges and risks at an organisation level. It adds all the skills and knowledge which you need to expertly handle projects and teams in a variety of industries.So, if you want to get a PMP® certification and still worried about if it would help you then you should keep aside your worries and get onboard for an opportunity to give your career a new direction by getting PMP® certified.

Rated 4.5/5 based on 14 customer reviews

Reap The Benefits Of Your PMP® Certification

Blogs

6595

Reap The Benefits Of Your PMP® Certification

by KnowledgeHut Editor
13 Feb 2019
12 mins read

What makes you stand out in the crowd as a PMP® c... Read More

Scrum Epic: What Is It And How To Create The Best Epics In Agile?

By Deepti Sinha

Scrum has been a buzzword since a decade now, and why not, it has so many success stories, hey, I am not talking about the stories which mean requirements in Scrum but the actual stories of teams and the organizations practicing Scrum. Looks like, I just gave the hint of what I would be covering in my article today.Yes, we will be talking about the requirements and how are they handled in Scrum. We will be talking about the Epic, so far, we have known Epic as a long narrative about the heroes of great historical or legendary significance performing courageous deeds but here we will touch upon a different side. Believe me, we are now going to talk about the EPICs in Scrum!What is an Epic in Agile?In simple terms, Scrum EPIC in Agile Methodology is a big chunk of work which can be divided into smaller user stories. An epic can be spread across sprints and even across agile teams. An epic can be a high-level description of what the client wants, and accordingly, it has some value attached to it. As we mentioned, an epic is a high-level requirement, hence its scope can change over the course of time.“Epics are a helpful way to organize your work and to create a hierarchy. The idea is to break down the work into shippable pieces so that large projects can actually get done and you can continue to ship value to your customers on a regular basis. Epics help teams break their work down while continuing to work towards a bigger goal.”- Atlassian To explain it better, I would prefer taking a life example, let’s say, throwing a New Year party at your place can be an epic requirement for you. To do so, you’ll need to organize your effort: from the biggest objectives down to the smallest details. You should be able to respond to change, report your progress, and stick to a plan. Once you are aware of the epic, you can drill it down to create smaller tasks like creating a guest list, deciding on the menu, shopping for the grocery, decoration at home, shopping for the new year, etc.Let’s see how we can create an Epic also called Scrum Epic User Story – In today’s era, almost all the tools that the team use have the capability to create an epic, it is up to the product and the team, which type of Epic they want.Some Epics cater to the reporting needs of management. Some Epics are created with a timeframe in mind, it should not be too long and too short, i.e. it should not take more than a couple of weeks to finish. But the widely used way is Storytelling.So, what is StorytellingStorytelling is a tool which helps you visualize the flow of events and how they corroborate back up to the Epic. If you feel, your working pattern does not sit in any of the mentioned ways, create your own. Just remember, Agile is never prescriptive, it shows you the path and how you want to go over it, it’s your choice!Coming back to our example, let us try to break it down into some doable components. It is really important to create chunks out of the epic so that the team can pick those up and deliver in a sprint time. You can compare this activity to art which requires precision in terms of size, priority, minimally interdependent etc. There are some pre-set ways of doing it, like:Workflow break downHere in our example, we talked about a project where we have a New Year party, let’s see how we can break it down in terms of workflow – Shopping can be a workflow where you need to get the items from outside. Another workflow can be cooking the food for the guests, same way we can have decorating the house as another workflow. See how simple it gets to understand once you start connecting it with our lives! This also helps the product owner to easily prioritize the work, in our case, the Product Owner can be the host of the party. Some steps in the workflow may not be important right now and can be moved to later stages. Perhaps baking the cake takes on the priority as it takes time to cool down but the same can be done later as well.Role-based breakdownWe can also break an epic as per the role or the persona, there can be different roles in your product or a project, here we have role of a ‘host’, ‘guest’ or you can have a role as a ‘cook’, you can even add the roles as per your product. In a role-based breakdown we talk in terms of that particular persona, example, for a host, ‘Driving a successful party’ can be one, for a guest, it can be, ‘Looking for some fun games at the party’.Break Down around the timelineSome of the epics can be broken down according to the time it will take to complete. The team usually divides the work which can be accomplished in a sprint time. They take up the whole thing, break it into pieces and fit the pieces in different sprints as per the dependency and priority. As I have already mentioned, the breaking down requires consideration into several areas such as size, priority, interdependency etc. Thus, there are two approaches to dividing – Horizontal and Vertical. It is like cutting the cake, if you cut it horizontally, you will get a single layer but if you take a vertical approach, you will get to have a bit of all the layers. Understanding the basic differences between Epic, Story, and TaskWe have been talking a lot about Epic and its breakdown, now let’s capture how it actually disintegrates further. We had an Epic “New Year Party”, this was a big chunk of work to be accomplished, we learned about the techniques to break it down. The result of the breakdown is termed Stories, which can be accomplished in a sprint time. The stories are further broken down into chunks called ‘Tasks’, the team pulls up the tasks and completes them, once all the tasks are completed, the story is marked as Completed. The below figure explains Scrum Epic Vs User Story:Thus,Epic - A requirement that is just too big to deliver in a single sprint. Epics need to be broken into smaller deliverables (stories).Story - A requirement that the business wants. It is something that is deliverable within a single sprint.Tasks - The essentials of a story, these are the milestones to take the story to ‘Done’.Anything that we cannot measure will not yield many results, we have been hearing this for a long time. It does apply here as well. We can use burndown charts to measure how much work has been accomplished in an Epic. This also helps in predicting if the team is on track with the commitments. By keeping a watch on the Burndown chart, it becomes easy to manage the progress and the blockers (if any) that the team is facing. This not only provides transparency to the system but it also helps in building the trust for the team and the clients.How to identify Epics in AgileEpic is something which is a fairly large chunk of work and cannot be completed at one go. It is something which requires discussion and brainstorming so that it can be broken down further into smaller chunks. At the epic level, we give rough estimates which can be in the form of T-shirt sizes, swags, points or any other method the team is comfortable with. The team can track the progress in an epic through the Burndown chart which represents the progress and also reflects if there are any blockers. Benefits of EpicsEpics help in understanding the high-level requirement from the stakeholder and what exactly is the need.It also helps in defining the scope of work which is in agreement with the client. Epics articulate efficiently about final output of user needs. Epics help to track bigger thoughts in a product backlog without the need to overwhelm it with multiple things. They allow establishing a hierarchy for the backlog items where the epic represents the original idea often closely related to a particular outcome.It also helps in estimating how much time it will take to deliver. Epics are time and again used as placeholders for new views that have not been thought out completely, or whose full expansion has been postponed till essentially desirable.Epics are then evolved into split into multiple user stories that help Agile development teams effectively manage and groom their product backlog.Common Pitfalls in EpicThough there are many positive aspects of using the epics in backlog management a coin always has two sides, it has its pitfalls too! Sometimes, the teams can create confusions around the end deliverable from the epic by just viewing them as more than just large user stories. This is deceptive when the team creates multifaceted tools to distinguish between epics and user stories as well as creates far-reaching tools for chasing epics separately from other backlog items.The teams may also try to estimate the epics at a very high level though they might not have a clear picture of what is to be done. This increases the chances of ambiguity and it is very likely that the estimates will not be of any use as it will not serve any purpose in reporting.Finally, here we are, with the discussions around the Epics and how we can break it down. There is no set way to work on the epic, it about what approach suits your needs. Again, it is all about the mindset and way we deal with the backlog. Epics are always fascinating to work with!

Rated 4.5/5 based on 12 customer reviews

Scrum Epic: What Is It And How To Create The Best Epics In Agile?

Blogs

9871

Scrum Epic: What Is It And How To Create The Best ...

by Deepti Sinha
12 Feb 2019
11 mins read

Scrum has been a buzzword since a decade now, and ... Read More

Search

Featured blog posts

Trending posts

Topics

Latest Posts

Who Is a Cspo? - Roles and Responsibilities

By Frederik Vannieuwenhuyse

Reap The Benefits Of Your PMP® Certification

By KnowledgeHut Editor

Scrum Epic: What Is It And How To Create The Best Epics In Agile?

By Deepti Sinha

Search

Trending blog posts

Featured blog posts

Trending posts

Topics

Latest Posts

Who Is a Cspo? - Roles and Responsibilities

By Frederik Vannieuwenhuyse

Reap The Benefits Of Your PMP® Certification

By KnowledgeHut Editor

Scrum Epic: What Is It And How To Create The Best Epics In Agile?

By Deepti Sinha