In today, I would like to discuss one of the most important aspects of Scrum. However, this aspect is often times neglected by organizations implementing Scrum. And that most important aspect is the Definition of "Done". Neglecting the Definition of "Done" is one of the reasons why we see a lot of failed scrum implementations in the market. Not putting enough emphasis on technical excellence in the Definition of "Done" is one of the reasons why we see a lot of products with technical debt in the market. If I can summarize scrum into a single line statement, it would be to continuously deliver a done increment that achieve the Sprint Goal every single Sprint. So because of these problems we found in the industry, in today's video I'm going to talk about the Definition of "Done" and the importance of "Done" in Scrum. Many of my future videos is going to refer back to today's video, so make sure you don't go anywhere to stay on this video. A lot of people think that the Definition of "Done" is the same as Acceptance Criteria.

Today I'm gonna talk about Who should be your Product Owner? Alright let's do this! Before we talk about who should be your Product Owner, let's talk about some of the misconceptions we often see in the market regarding the Product Owner role. There is a common misconception in the market that the Product Owner is just another name for a business analyst who writes the user stories for the development team. A lot of companies think that the Product Owner is a tactical role and only play at the Scrum team level. So that's why a lot of companies assigns the Product Owner role to the business analysts.

Why should a developer choose to work in the company product or outsourcing? If you love bringing value products into the hands of users and play an active role in the development of the product over time, the company product, such as Atlassian (is an Australian enterprise software company that develops products geared towards software developers and project managers), is probably the place for you. If you want to work in multiple projects, many different products over time, the company outsourcing should be your home.

n today's whiteboard session, I'm going to cover Agile project management in about 180 seconds, so let's get stuck in. Now, first thing you need to know is that Agile project management methodology is not an approach for every single project. It's only good for projects where the end user may not know exactly what they want. You have kind of also the constant variable changing priorities and you have access to a cross functional team of people who can collaboratively work together at the same time, ideally co-located. If you've got those ingredients, then you certainly have everything, at least at the starting point where you might want to try and approach the project using Agile project management.

I got a question about programming until old. This question is from Apaven I think. He says, “Last weekend I have discussed a software developer job with my friends about software developer is a dead end job or not. Later I tried to look on the internet and found some good arguments from both sides. Here is a sample about programming as a dead end job.” He’s got a quote from a story here, and he says, “Many programmers find that their employability starts to climb at around age 35. Employers dismiss them as either lacking in the technical skills such as the latest programming language fad or not suitable for entry level, in other words, either unqualified or overqualified. That doesn’t leave much, does it? It’s a sick show that most software developers are out of the field by 40. Employers have admitted this in unguarded moments. Craig Barrett a former chief executive officer of Intel Corp famously remarked the half life of an engineer software or hardware is only a few years while Mark Zuckerberg of Facebook has blurted out that young programmers are superior. I’m not satisfied with the results from my searching, so I would like to know your opinion about this issue.”

In today, I'm going to be answering the question "Who should be in the development team?". In every Professional Scrum classes that I have facilitated so far, most probably I will get this question "Who should be in the development team?". People often ask me: should Quality Assurance be in the development team? Should Business Analysts be in the development team? Should User experience (UX) professionals be in the development team? After all they are designers right? They are not developers. How about people from audit? People from governance? People from risks? How about data scientists? Should they be in the development team?

In today, I would like to talk about technical debt specifically in software development. This is one of the topics that I'm passionate about. In fact one of the reasons why I'm interested with Scrum is not only because Scrum emphasize heavily on the people aspect in software development but also because Scrum as taught by Ken Schwabe, one of the co-founders of Scrum, emphasize heavily on technical excellence and professionalism in software development. Interestingly if we look around us, there are more and more organizations using Scrum in our industry and at the same time I also see many organizations care less about technical debt in the product they develop. A lot of people from the business, a lot of managers think that Scrum is only about delivering products fast

Today, I would like to share with you the answer to one of the most common questions that I get from people that is: "Can the Scrum Master also be the Scrum developer or can one person play both the Scrum Master and the Scrum developer role?". And before we get into this I will share with you some common reasons why companies may want one person to be both the Scrum Master and also play the Scrum developer role. The first reason why a lot of companies ask one person to be the Scrum Master and also be part of the Scrum developers is because the Scrum Master role is not fully understood yet in the company

I'd like to share about how to evaluate the Scrum Master's performance. The reason why I want to talk about this topic is because just a few months ago, a CEO of a multinational company, who is also my client, asked me: I've got so many Scrum Masters in the company, how do I know which one is valuable to the company? How do I know which one I should retain or not?. If you're also interested to learn more about this topic, don't go anywhere stay tuned. As you have seen on my previous video on the Scrum Master stances, the Scrum Master uses several stances to improve the organization agility.

If you're an aspiring Scrum Master, don't go anywhere, stay tuned. The key to be an Awesome Scrum Master is balance, that is knowing when to use the right stances within the right context. The Scrum Master uses several stances to improve the organization agility, that is the teaching stance, mentoring stance, coaching stance, leadership stance and facilitation stance. To explain what stances the Scrum Master should be using according to the context that the Scrum Master is experiencing,

I think in today's I'm gonna talk about how to recruit awesome Scrum Masters from the job market. The reason why I want to talk about this topic is because last week when I was in Melbourne somebody asked me to have a chat over coffee and he asked me what are the things to look out for when recruiting for Scrum Masters from the job market. During the conversation, I didn't have any kind of list or criterias, the conversation just emerges and flows through. After having that conversation I jot down the list, the things that I've been using when I'm looking out for Scrum Masters from the job market over the past few years.

In today's video I'm gonna be talking about "How to use Scrum with DevOps". Yes I do know that Scrum and DevOps does not conflict with each other and in fact they complement each other. But from time to time I keep on getting questions from people whether they should use Scrum or DevOps. So in today's video I'm gonna bust the myth that you cannot use Scrum and DevOps together. If this is something for your appetite, stay tuned don't go anywhere folks. A lot of people think that DevOps is only about tools. Well it really depends on who's promoting DevOps.

The reason why I want to talk about this topic is because recently I received so many questions from people who have the title Product Owner in the company but quite unsure whether they really are the Product Owner. It's quite ironic to see so many people in our industry to have the title Product Owner but not really the Product Owner. So let's see the indicators to identify whether someone is really the Product Owner;. If you are interested with this topic, stay tuned, don't go anywhere folks. The first indicator to use to identify whether someone is really the Product Owner is by looking at how the individual spend his or her time within one Sprint.

In today's let's talk about Product Owner stuff. Let's talk about how to order the Product Backlog. This is important because there are still a lot of misconceptions out there. There are still a lot of articles and YouTube videos that says that the Product Backlog is prioritized. According to Scrum Guide the Product Backlog is ordered instead of prioritized. There are reasons why the Product Backlog is ordered and there are multiple aspects that Product Owner need to consider when ordering the Product Backlog. So if you are curious what are the aspects that the Product Owner need to consider when ordering the Product Backlog don't go anywhere stay on this video

n today's, let's talk about something really important, that is the differences between project management and product management because there are still growing misconceptions in the market. A lot of people still think that Scrum is an agile project management methodology. Let's bust the myth because Scrum is a product management framework. If you're curious about the differences between project management and product management, stay tuned sit back and relax because I'll be back right after ... this. When comparing project management and product management, we must first compare the definition of project and product

In today's, let's talk about the accountability and the responsibility of a Product Owner. We've seen in the market how there are so many people with the title Product Owner but mostly only fiddle around with that user stories in JIRA, which makes them more like a Product Scribe. Is this what the Product Owner should actually do? Oftentimes people are not doing as intended because they do not know their accountability and their responsibility. If you would like to know the Product Owner's accountability and responsibility, stay tuned, don't go anywhere, because I'll be back right after this.

The chances are that you've just done a search for the difference between Scrum and kanban, you've come to the right place. Not only do I have a great video for you, I also have a cheat sheet for you to download. Hi this is Gary Straughan Welcome to Development That Pays Scum and Kanban are perhaps the best known of a number of Agile software development methodologies Let's break that down. Software Development looks like this: The Product Owner decides what to build The Development Team builds it and Customers use it, experience it, benefit from it in some way What makes software development AGILE is that VALUE is delivered to the customer in small increments And, IMPORTANTLY, feedback is gathered from customers and fed back into the process.

Let's talk about Agile Software development from the perspective of the Product Owner Here's Pat, she is a Product Owner. She has a product vision that she is really passionate about She doesn't know the details of what our product is going to do, but she knows why we are building the product What problem it's gonna solve, and for who She talks about all the time. Here are the stakeholders They are the people who are going to use and support or in any way be affected by the system being developed. Pat's vision is that these people here will love our system and use it all the time and tell their friends about it. The stakeholders needs and Pat's ideas are expressed as user stories, here.

nitially I started my own YouTube channel just to improve my creativity as a Scrum Master as it is important for the Scrum Master to be creative. I didn't realised that a lot of people actually found values in my vlogs. So thank you once again and let's start today's video. So in today's video I would like to discuss about the differences between project manager and Product Owner. This topic was requested by Dejan Majkic on my previous video about project manager versus Scrum Master. So if you're also interested to know about the differences between project manager and Product Owner, don't go anywhere stay on this video.

Introduction to scrum a seven minute training video with details on what you need to start using scrum today this video is intended for people who are just getting started with the scrum framework and need a quick primer hi my name is Steve Steadman and I am the founder of utility software in this video we will cover the basics behind scrum and we'll take a look at how scrum compares to waterfall development and will examine the three roles three artifacts and three ceremonies that make up scrum first let's take a look at how scrum compares to the older alternative of waterfall development waterfall typically goes through a lengthy planning process which could take several months followed by building the product which again could take many months and then testing the product reviewing