7 episodes

Welcome to the Scrum Institute Podcast!

This podcast is for professionals and students who want to learn how to deliver great software in a way that lets us get our mission, our products, and our services, out to the world… and yet still learn necessary skills as economically as it is possible.

Learn from International Scrum Institute, the world-famous Scrum training, and certification organization, which successfully certified more than 628,700 people from all counties around the globe.

Inside each episode, Scrum Institute shares the biggest “a-ha moments” and software engineering secrets with complete transparency. From tough lessons learned, to mindset, to pure delivery strategy, Scrum Institute pulls you into a world of real engineering and business professionals, and shares journeys and secrets of many organizations to building great software, with NO firefighting.

Scrum Institute Address: www.Scrum-Institute.Org
Scrum Institute Podcast Address: www.ScrumInstitutePodcast.com

International Scrum Institute Podcast International Scrum Institute, Scrum-Institute.Org

    • Courses

Welcome to the Scrum Institute Podcast!

This podcast is for professionals and students who want to learn how to deliver great software in a way that lets us get our mission, our products, and our services, out to the world… and yet still learn necessary skills as economically as it is possible.

Learn from International Scrum Institute, the world-famous Scrum training, and certification organization, which successfully certified more than 628,700 people from all counties around the globe.

Inside each episode, Scrum Institute shares the biggest “a-ha moments” and software engineering secrets with complete transparency. From tough lessons learned, to mindset, to pure delivery strategy, Scrum Institute pulls you into a world of real engineering and business professionals, and shares journeys and secrets of many organizations to building great software, with NO firefighting.

Scrum Institute Address: www.Scrum-Institute.Org
Scrum Institute Podcast Address: www.ScrumInstitutePodcast.com

    Scrum Institute, Scrum Framework Episode #7

    Scrum Institute, Scrum Framework Episode #7

    Scrum Institute, Scrum Framework Episode #7 has been proudly brought to you by International Scrum Institute, https://www.scrum-institute.org



    You can also listen Scrum Institute’s Podcast from Apple, Spotify, Castbox and Google Play.



    Scrum Institute Podcast on AppleScrum Institute Podcast on SpotifyScrum Institute Podcast on CastboxScrum Institute Podcast on Google Play



    What Can Cause Chaos And Frustration Before The Scrum Framework? This Might Surprise You!



    To better understand the impact of the scrum framework to our software engineering practices and businesses, it makes sense to have a look at a day in the life (or a software project in life). 



    Therefore, I would love to briefly talk about a software project from the past before we adopted the scrum development and software delivery framework in our organizations. 



    A few days before I wrote these lines, we had lunch with one of my ex-colleagues with whom we used to work together almost 20 years ago. 



    This gentleman, Marcus has got his scrum master certification and scrum product owner certification from International Scrum Institute. He currently works as a scrum master for one of the leading software houses in the agile project management software domain. 



    As a scrum master, Marcus is now in charge of operating an agile scrum team whose scrum team members located in geographically distributed locations around the globe. 



    During our lunch, Marcus admitted that there are a lot of typical challenges with distributed agile scrum teams. Some of the problems he specifically mentioned related to his software project configuration are: 



    Differences in working styles among scrum team members, Timezone differences,Cultural misfits, andLanguage constraints. 



    Despite these difficulties, Marcus still added that running a software project with the agile scrum process is more fun, productive, and enriching than how we used to work 20 years ago. Compared to days when we used to work without scrum software development and scrum software delivery processes. 



    Marcus’ statement was indeed a big testimonial for the credit of the scrum framework from a very accomplished and experienced manager, scrum master, and product owner. 



    Thank you, Marcus! 



    Then we explained to him one of our past software projects before we used to meet with the scrum framework. I’m sure that many scrum masters would resemble this experience to their previous projects before they’ve gotten their scrum master certifications. 



    Back in the late 1990s, we were part of a software engineering group to build a smart card-based public key infrastructure. Smart cards securely protected private keys of infrastructure members, associated public keys and their wrapper certifications were openly distributed (as the name public implies). 



    Back in the day, this was by itself a relatively complex IT project that required multiple interdependent hardware engineering and software engineering teams. We had to do massive amounts of research and development (R&D) to build a fully functional hardware and software system. 



    Remember these are days before we had the minimum viable product (MVP) concept to experiment, create, learn, and experiment again. 



    Without scrum to create such a sophisticated infrastructure that constituted numerous hardware and software elements was a real challenge. 



    Here are three significant setbacks we used to have without any scrum masters and anyone who possesses a scrum master certification in our teams.



    Had To Plan The Entire Project Before Understanding The Project? This Might Surprise You!



    Without scrum, our teams had built and delivered entirely wrong software and hardware products that did not fulfill demands from our client.



    We had times in our professional lives when some third

    • 18 min
    Scrum Institute, Scrum Framework Episode #6

    Scrum Institute, Scrum Framework Episode #6

    Scrum Institute, Scrum Framework Episode #6 has been proudly brought to you by International Scrum Institute, https://www.scrum-institute.org



    You can also listen Scrum Institute’s Podcast from Apple, Spotify, Castbox and Google Play.



    Scrum Institute Podcast on AppleScrum Institute Podcast on SpotifyScrum Institute Podcast on CastboxScrum Institute Podcast on Google Play



    Learn Scrum Framework Using Real World Case Study! This Might Surprise You!



    Before Starting The First Sprint



    Alex works as the Scrum Product Owner of a new software development project. One of his first tasks is to assess and find out requirements to deliver business value his client is looking for. 



    He needs to make sure that his client will get the correct software to achieve tangible business results. He writes down the essential use cases and discusses them with the architects, client representatives, and other stakeholders from IT and business units. 



    After assembling the high-level use-cases and requirements, he writes them into the Scrum Product Backlog and initiates an estimation and prioritization session with the Scrum Team. As a result of this session, all items in the Scrum Product Backlog get an initial rough estimate and priority.



    During those sessions, Anna, the Scrum Master, ensures that everyone speaks the same language. So, the Scrum Product Owner, the Scrum Team Members, and their stakeholders arealigned with the anticipated goals. So they have an adequate understanding of potentially new concepts for them, such as Use Case, Backlog, Sprint, and so on. And most importantly, the Scrum software development and delivery process is correctly applied in the store.



    Now Alex, the Scrum Product Owner, begins to break down the high-level requirements into the first draft of smaller-grained user stories. With this list, he then calls for the first Sprint Planning Meeting. 



    Sprint 1 – Day 0 



    During the Sprint Planning Meeting, Alex presents the Scrum Product Backlog items from the highest priority to the lowest. The Scrum Team asks and clarifies open questions. For each item, the team discusses if they have enough 25 capacity and the required know-how to develop and deliver it. The Scrum Team needs to ensure that all required human and technical resources are in place before the start of the Sprint. They need to confirm that all prerequisites and dependencies are fulfilled, which could be critical to delivering certain software features successfully.



    During Sprint Planning Meeting (What-Part), the Scrum Team commit to complete the user stories 1,2,3,6,7 and 8 until the end of the Sprint. So these user stories are now moved from the Scrum Product Backlog to the Sprint Backlog. The user stories 4 and 5 cannot be accomplished in this Sprint, as some prerequisite technical infrastructure is not yet in place. 



    After the What-Part of the Sprint Planning Meeting, Anna, the Scrum Master, calls the Scrum Team to drill down how the team is going to implement the committed user stories (How-Part). The emerging tasks during the How-Part of the Sprint Planning Meeting are written down on the cards, and the team store them into the Sprint Backlog. Now all members of the Scrum Team are ready to select a task to begin to work on. 



    Sprint 1 – Day 1



    In the morning, the whole team gets together for their Daily Scrum Meeting. Everyone gives a brief and concise statementabout what he or she has done so far, updates the estimates of remaining work on the cards of the Sprint Backlog. Everyone tells what he or she is planning to do today, and reveals if there are any impediments which hinder them from processing any tasks. 



    Today one of the Scrum Team members, Melinda, informs the Scrum Team that she has a problem with the license of the integrated software development environment she is usi

    • 9 min
    Scrum Institute, Scrum Framework Episode #5

    Scrum Institute, Scrum Framework Episode #5

    Scrum Institute, Scrum Framework Episode #5 has been proudly brought to you by International Scrum Institute, https://www.scrum-institute.org



    You can also listen Scrum Institute’s Podcast from Apple, Spotify, Castbox and Google Play.



    Scrum Institute Podcast on AppleScrum Institute Podcast on SpotifyScrum Institute Podcast on CastboxScrum Institute Podcast on Google Play



    What Are The Five Key Values Of The Scrum Framework? This Might Surprise You!



    We have already mentioned that the scrum framework is not only a software engineering process. It also has a robust set of underlying principles. 



    In fact, most of the professional business domains can apply and utilize these principles.



    It’s not enough to get a scrum certification to be hugely successful with the scrum. You should possess a firm grasp for scrum values to succeed with the Scrum framework 



    So that you’re going to deliver a great job and fantastic software that your customers and employers love. Let me now tell you more about those principles of the scrum process. 



    Scrum Value #1. Courage



    There are times when doing the correct thing to serve the best values and benefits for our clients are not the easiest. In such moments, scrum master, scrum product owner, and the scrum team members should remember their duty and obligation. 



    That’s to build the best possible products and services in their particular business and information technology domain. To be better than mediocre, a scrum team should sooner or later face difficult decisions that won’t make everyone happy in their particular ecosystem of stakeholders.



    To deal with this, all members of the scrum team should remember what they learned during their scrum certification training. 



    They should remember to be courageous, and they should master to decide and act courageously.



    Scrum Value #2. Focus 



    With the scrum framework, when you hear the value focus, you should be thinking about two things: 



    Identification of correct work:  What tasks are necessary to deliver the goals of my sprint? What are essential to developing the best software products and services for my clients so that they will be pleased with my work?Prioritization: What tasks should I be working on next?



    Each moment in time, there is one critical question that the entire scrum team, including scrum master and product owner, must be answering. 



    This question is: “What are the most important things we should be doing at the moment to fulfil reasons of why an employer hired us in the first place?” 



    Scrum framework has several built-in events (rituals) to ensure the reasonable prioritization of user stories and tasks. According to the scrum process, the prioritization of user stories and their associated tasks should have a continuous priority. 



    So we make sure that the scrum team works on the right things in the correct order. 



    Some of the built-in scrum ceremonies (scrum events) to prioritize our work and adjust our focus are: 



    Scrum Grooming (Backlog Refinement) Meeting: Grooming Meeting solely focuses on prioritization for Product Backlog to prepare it before the upcoming Sprint Planning Meeting.Sprint Planning Meeting: These meetings help us see the dependencies and correct order of work to deliver our user stories.Daily Scrum Meeting: Daily Scrum (Daily Stand-Up) Meeting supports us to set the tone of an upcoming workday. We must direct our focus on where it’s most required.Sprint Review Meeting: Sprint review meeting indirectly shows us where the emphasis of the 21 scrum team must be channeling to have more successful reviews in the future.Sprint Retrospective Meeting: These meetings support the scrum team to prioritize what aspects of their engineering process must be first improved.



    Here in this section, I covered scrum rituals only from a focus

    • 8 min
    Scrum Institute, Scrum Framework Episode #4

    Scrum Institute, Scrum Framework Episode #4

    Scrum Institute, Scrum Framework Episode #4 has been proudly brought to you by International Scrum Institute, https://www.scrum-institute.org



    You can also listen Scrum Institute’s Podcast from Apple, Spotify, Castbox and Google Play.



    Scrum Institute Podcast on AppleScrum Institute Podcast on SpotifyScrum Institute Podcast on CastboxScrum Institute Podcast on Google Play



    What Is Self Organization In Scrum Framework? This Might Surprise You!



    The scrum team organizes itself. Scrum team members decide in consensus about tasks they need to execute to deliver the goals of a sprint. A self-organized team doesn’t require a manager or a team leader. 



    Self-organization in the scrum framework is very disciplined. 



    Sprint Backlog, Sprint Burn down Chart, and Daily Scrum Meetings which you are going to learn more about them later in this material build the foundation of self-organization. 



    Organizing the work by themselves requires for the most teams a learning phase. Competent scrum masters who own scrum master certifications support their scrum teams to excel with self-organization quickly. 



    Self-organization also includes the ability to work together despite different opinions and possible conflicts among various scrum team members. Self-organization requires compliance and trust in joint decision-making processes.



    Those decision-making process in the scrum framework includes, but not limited to, planning, estimating, implementing, reporting, and reviewing the work the scrum team is jointly responsible.



    Yes? Then you need to bring up a team that can self-organize its own work!



    What Is Inspect And Adapt In Scrum Framework? This Might Surprise You!



    Scrum Inspect and Adapt is a straightforward concept to comprehend, but the hardest to properly implement and master.



    Companies have finally confirmed that none of their project managers can fully foresee the big picture of complex systems. They were unable to do reliable end-to-end planning. It was evident for them that they needed to try something different. 



    Together with lean manufacturing (also known as lean movement), companies needed to develop a process to empower them strategically. They needed a standard operating procedure to help them learn and fix their courses of action while they’re running their projects and even operations.



    That was the birth of Toyota Improvement Kata, which we today call “Inspect and Adapt” while we talk about scrum software development and delivery framework. 



    According to “Scrum Inspect and Adapt”: 



    Step 1. Inspect: We do our best to grasp the current status of the project with our current level of know how and understanding about it. Step 2. Adapt: We define a direction and vision about the next steps of our project and then strategize and execute our vision. Step 3. Learn:  We carefully observe, learn, and teach each other while we do so. We continuously log what works and what doesn’t work while we do our work.Step 4. Restart:  Start over from Step 1 again.



    Note that those four steps described above are analog, but not limited to the following Scrum rituals (Scrum events). 



    Step 1. Inspect is analog to Sprint Review Meetings and Sprint Retrospective Meetings.Step 2. Adapt is analog to Sprint Planning Meetings and Backlog Refinement Meetings.Step 3. Learn is analog to Daily Scrum Meetings.Step 4. Restart is analog to the closure of a sprint and the start of a new sprint.

    • 3 min
    Scrum Institute, Scrum Framework Episode #3

    Scrum Institute, Scrum Framework Episode #3

    Scrum Institute, Scrum Framework Episode #3 has been proudly brought to you by International Scrum Institute, https://www.scrum-institute.org



    You can also listen Scrum Institute’s Podcast from Apple, Spotify, Castbox and Google Play.



    Scrum Institute Podcast on AppleScrum Institute Podcast on SpotifyScrum Institute Podcast on CastboxScrum Institute Podcast on Google Play



    What Is Agile Manifesto? This Might Surprise You!



    When the IT industry talks about the Scrum framework, It’s also often we hear the term “Agile Scrum” along the same lines as “Scrum”. It led some of us in the industry to think and look for differences between the terms “Agile Scrum” and “Scrum”. 



    Here is good news for you. “Agile Scrum” and “Scrum” terms do both refer to the same thing. They both refer to the Scrum software engineering process. Then why do we sometimes use the word “Agile” in front “Scrum”?



    It’s because the scrum framework fully embraced and embedded the Agile Manifesto (Manifesto for Agile Software Development) to its core process, principles, and underlying philosophy. That brings us to understand the agile manifesto and the values of the scrum process better before we deep-dive the technicalities of the scrum process.



    Agile manifesto values: 



    Individuals and interactions over processes and tools, Working software over comprehensive documentation, Customer collaboration over contract negotiation, Responding to change over following a plan.



    While the factors on the right-hand side do still possess significant values, the agile manifesto appreciates and prioritizes the factors on the lefthand side higher.



    The elements favored by the agile manifesto have been carefully time-tested and chosen to: 



    Serve clients and stakeholders better and create value for them with software, Enhance the profession of software engineering regardless of your role, title, and career level.

    • 2 min
    Scrum Institute, Scrum Framework Episode #2

    Scrum Institute, Scrum Framework Episode #2

    Scrum Institute, Scrum Framework Episode #2 has been proudly brought to you by International Scrum Institute, https://www.scrum-institute.org



    You can also listen Scrum Institute’s Podcast from Apple, Spotify, Castbox and Google Play.



    Scrum Institute Podcast on AppleScrum Institute Podcast on SpotifyScrum Institute Podcast on CastboxScrum Institute Podcast on Google Play



    What Is The Scrum Framework? This Might Surprise You!



    What is Scrum? Well, without making things too complicated, the Scrum framework can be defined as the following: 



    Scrum is an iterative software engineering process to develop and deliver software. 



    Although the software is the main focus of the Scrum framework, iterative and agile Scrum process can be and is already being applied outside the software industry as well. 



    Most people in the IT industry believe that the term “Scrum” was coined early in the 2000s as a parallel track of emerging agile software development and delivery trends. That is a piece of incorrect information!



    The term “Scrum” was first used and published by Harvard Business Review in January 1986. Hirotaka Takeuchi and Ikujiro Nonaka coined the term “Scrum” with their article: The New New Product Development Game. (Yes, two News) You should have a look at “The New New Product Development Game” to see how everything all about Scrum got started!



    Scrum can be used in all kinds of software development projects. To develop and deliver complete software packages or only some modules of larger systems — both for products and services of internal and external clients. 



    The Scrum Framework is a lightweight process. It focuses on increasing the productivity of teams while reducing wastes and redundant activities.



    Scrum defines some general guidelines with a few rules, roles, artifacts, and events. Nevertheless, all of these components are critical, serve for specific purposes, and they are essential for the successful use of the Scrum framework. 



    The main components of Scrum framework are: 



    Three Scrum Roles: The Scrum Product Owner, the Scrum Team, and the Scrum Master.Five Scrum Events (Scrum Rituals) or Ceremonies: Scrum Grooming (Backlog Refinement) Meeting, Sprint Planning Meeting, Daily Scrum Meeting, Sprint Review Meeting, and Sprint Retrospective Meeting.Product Backlog (Scrum Backlog) or Scrum Product Backlog: An artifact that is used to manage and prioritize all of the known requirements of a Scrum project.Sprints: Cycles of work activities to develop shippable software product or service increments.Sprint Backlog: An artifact to keep track of requirements committed by the Scrum teams for a given Sprint.



    Self-organization and unconditional collaboration are critical elements of the Scrum framework. Scrum Teams do no longer require a project manager in a classical sense. With the Scrum framework, the Scrum Master and the Scrum Product Owner share the role and responsibilities of a typical project manager. 



    Nonetheless, a Scrum Master or a Scrum Product is never allowed to overrule the democratic decision-making capability of a Scrum Team. For instance, only the Scrum team members can jointly commit which ones of highly prioritized Backlog items they will deliver in a Sprint as a software increment. 



    Another central element with the Scrum framework is the continuous improvement that we enable with “inspect & adapt”. A Scrum Team continuously monitors, inspects, and assesses their artifacts and their use of Scrum framework to adapt and optimize them. These continuous efforts for optimization maximize quality, efficiency, client satisfaction, and therefore minimize wastes and overall project risks. 



    The Scrum framework understands that the requirements are likely to change and they are not entirely known, especially at the beginning of pro

    • 7 min

Top Podcasts In Courses