<\/a><\/p>\n Before we dive into how Agile and Scrum can make your projects a whole lot smarter to manage, let\u2019s talk about what the difference between the two is.<\/p>\n While born out of revolutionizing software development, Agile initially started as a way to create better software products more efficiently. But today, Agile is so much more than that. It extends to worlds outside of IT and finds creative uses in almost any field of work.<\/p>\n Commonly, you might hear Agile being called a methodology. All that means is that it\u2019s a set of conventions that a team agrees to follow. If you\u2019re managing a project and using the Agile methodology, then you and your team have chosen to follow a way of working that is highly collaborative and quick to change course to deliver the best outcome.<\/p>\n We can also understand Agile as being less structured than a methodology. In its simplest form, Agile is a mindset.<\/p>\n When you have an Agile mindset, you aren\u2019t afraid of change\u2014and making those changes quickly. For example, if your business is a bakery, you may envision making lots of cheesecakes, but then you get feedback from your customers saying that most of them are lactose intolerant. Instead of making cheesecakes, you quickly pivot to making dairy-free pies. Having an Agile mindset in project management is what helps you be adaptable.<\/p>\n While Agile is a methodology (or mindset), Scrum is a framework to put Agile into practice.<\/p>\n Scrum is based on empiricism, which says that knowledge comes from experience and making decisions based on what is known<\/a>. If you\u2019ve heard people praise the idea of \u201ctest and learn\u201d before, then you\u2019re already kind of familiar with Scrum.<\/p>\n It simply refers to quickly improving by testing out a new idea by only focusing on what\u2019s important, seeing how it does, then learning from the failures so that you can pivot efficiently.<\/p>\n Instead of working in a linear fashion, Scrum allows you to break work up into modules so that you can see results sooner and adapt to change easier. It involves close cross-functional collaboration<\/a> and timeboxing each incremental piece of work. More on that to come as we deep dive into the 5-step framework in the next section.<\/p>\n For now, let\u2019s go over the three pillars to Scrum:<\/p>\n Although originating from software development, there\u2019s no limit to the type of work that can benefit from Scrum. If you have a project where you need to create an end-product, then applying the principles of Scrum will allow you to manage the project to deliver results faster.<\/p>\n Whether you\u2019re on the marketing team and need to push out ads for a campaign, or in sales and need to create a pitch deck, Scrum has a role to play in most parts of your business\u2014that is, if you know how to use it. And if you\u2019re not sure, don\u2019t worry, keep reading.<\/p>\n The next time someone uses the words interchangeably\u2014correct them!<\/p>\n Agile is the \u201cwhat\u201d, while Scrum is the \u201chow to.\u201d That is, Scrums is one way of how to implement Agile project management. The Scrum framework is an actionable set of steps to carry out an Agile project. It\u2019s a way to break a project down into manageable sprints, which are set periods of time where the team completes parts of the project. Sprints can be from anywhere between one to four weeks in lengths, based on the complexity of your project. Coming out of each sprint is an incremental completion of the overall project.<\/p>\n In the Scrum model, there are four key roles to consider when organizing a team:<\/p>\n Together, these four roles come together to execute on specific events using the Scrum framework:<\/p>\n Owned by the Product Owner, the product backlog is a list of all the deliverables to come out of the project, prioritized by importance; basically, this is a to-do list. At this stage, this list isn\u2019t exhaustive. While you should list out every known thing you know will be created, keep in mind that the product backlog is still a dynamic asset and not set in stone. Over the course of the project, as product needs are discovered and changed, so too should the product backlog be updated.<\/p>\n With the product backlog in hand, the team is ready to meet and divvy out responsibilities. At the start of each sprint, hold a planning meeting to decide on which product backlog item(s) to focus on and what can be achieved during the allocated sprint time. The planning meeting should be timeboxed based on how long the sprint will last<\/a>:<\/p>\n If you have remote team members, use communication tools<\/a> to your advantage. For example, the RingCentral app<\/a> allows you to message, call, and meet over video. Get that quick face-to-face communication<\/a> even if you\u2019re miles away: Coming out of the sprint planning is a subset of the product backlog to be tackled during the sprint, called the sprint backlog. If new work that needs to be done is discovered during the sprint, it\u2019ll be added to this backlog. In terms of accountability, while the Product Owner is responsible for the product backlog, the actual hands-on project team is responsible for the sprint backlog.<\/p>\n Also known as the daily standup, this is a short 15-minute meeting at the start of every sprint day with the Scrum Master and the project team (the Product Owner and other stakeholders are optional). Normally held at the same time each morning, each person stands and shares what they did yesterday, what they\u2019re going to do today, and raise any challenges or obstacles they need help with. This quick touchpoint keeps members accountable and collaboration tight.<\/p>\n At the end of each sprint, an informal sprint review is held with the Product Owner, Scrum Master, project team, and relevant stakeholders. If you recall from before, \u201cinspect\u201d and \u201cadapt\u201d are pillars of Scrum, which are highlighted at this stage. The project team does a show-and-tell (\u201cdemo\u201d) of the work completed and collects feedback from participants.<\/p>\n Also, they\u2019ll do what is called a sprint retrospect, which is basically an unwinding process where team members share what went well, what didn\u2019t go so well, and what can be improved on for the next sprint.<\/p>\n Sprint cycles continue until all items on the product backlog are complete\u2014marking the project as done. If you\u2019re ready to put Agile project management with Scrum into practice, start by creating the product backlog by checking out this example and template<\/a> to get a hang of what\u2019s involved.<\/p>\n Once the backlog is established and before heading into sprint planning, make sure that every participant knows their role well in advance.<\/p>\n Create a checklist (or check out this<\/a> one!) to prepare for the planning meeting and itemize actions that need to happen during the meeting. Don\u2019t forget to send out an agenda<\/a> in advance to all participants so everyone knows what to expect.<\/p>\n At this point, you should consider creating your sprint backlog and tracking sprint progress in an Agile project management tool<\/a> (scroll down to see which ones we recommend).<\/p>\n A popular way to see how the team is progressing throughout the sprint is via a visual task board. At minimum, this should include the columns To Do, Doing, and Done. These headings can be adjusted to be relevant to your project. For instance, if your project is creating a social media campaign, then your task board can track for Content Ideas, Drafting, In Review, and Published.<\/p>\n This task board idea is called the Kanban method, which is a popular technique used in Agile project management. It allows you to quickly visualize the workflow and helps the team manage the amount of work at hand appropriately (by not piling on more items in the To Do column than can be handled).<\/p>\n For more complex projects with more variables, you could also consider workflow management tools<\/a> that let you add in columns to track Needs Assistance, Dependencies, or Hold For Now. This is where free project management software<\/a> could help you organize your process.<\/p>\n For smaller projects, and especially if experimenting with using Scrum and Kanban boards for the first time, you might not want to invest in fancy, high-end virtual tools. In that case, start out with just paper and markers. It\u2019s more common than you think.<\/p>\n Plus, it doesn\u2019t need to be glamorous, it just needs to help the team stay organized<\/a>. Remember, this board will be refreshed with every sprint (one to four weeks) so if it evolves into minor chaos\u2014remember that it\u2019s just temporary minor chaos.<\/p>\n If going with a physical board option, set up a dedicated open space for team members to easily access and have supplies (different colored markers and sticky notes) readily at hand. Also, consider using this area to hold daily scrum meetings.<\/p>\n<\/div>\n Another option is to use a mix of virtual and physical resources.<\/p>\n While a physical board takes up space, it promotes the opportunity for face-to-face communication and better problem solving. In-person interactions facilitate greater chances for collaboration and quick resolutions.<\/p>\n At the end of each day, the Scrum Master can input all the items on the board into a virtual tracker. This is useful for documenting the process to help future Agile users learn from your process or for presenting to stakeholders to illustrate progress. Imagine you have a bow and arrow that you\u2019re using to shoot at a moving target. There are two ways to do this: the traditional way and the Agile way.<\/p>\n Using Agile, you keep adjusting based on external factors that are revealed overtime. Maybe the wind changes direction or the target\u2019s movement becomes irregular. Whatever these unknown factors are, you hone in quickly, making them known so that you can best adapt.<\/p>\n Similarly in business, everything is a moving target. We live in a world of unknowns where not everything is in our control. You plan for a massive product feature to be released in a year\u2019s time, but suddenly the economy faces a downturn, new competitors rise, or customer needs change. Now what?<\/p>\n You need ways to manage your project upfront to build in flexibility, collaborate with different knowledge sources, and sustain momentum. Enter Agile project management. Let\u2019s take some of the mystery out of Agile and look at some practical ways you can get started right away.<\/p>\n If you\u2019re looking to experiment with the Agile methodology, don\u2019t be afraid to start small. While most effective in managing complex projects, Agile can be just as effective when used on simple projects.<\/p>\n Take an inventory of all the upcoming projects on the horizon. These could be straightforward such as upgrading office space or recreating business proposal templates. Or, they can be more nuanced such as upgrading a customer-facing product feature.<\/p>\n Whatever it is, choose an initial project that:<\/p>\n Remember, this is a chance for you to experiment with a new way of working. That \u201ctest and learn\u201d attitude we touched on earlier? This is the time to embrace it.<\/p>\n Once you\u2019ve selected the right project, identify team members who will be involved. Since this is the first time your business will be trying out a new approach, you want to get the right people on board. Team members who can set a good example and eventually be advocates for using Agile are good choices to keep in mind. Remember, based on the Scrum model, there are four key roles to consider when organizing an Agile team: the Product Owner, the Scrum Master, the project team itself, as well as its stakeholders.<\/p>\n And don\u2019t forget, your team doesn\u2019t all need to be in the same office for your Agile project to work. Software like RingCentral Video<\/a>, can help bring remote team members together to work through backlog meetings and daily scrums:<\/p>\n <\/p>\n You may already have tools you\u2019re using to manage projects, which you want to stick with. There\u2019s both pros and cons to that.<\/p>\n Pro, because you and your team are likely fluent and familiar with its ins and outs.<\/p>\n Con, because the same familiarity could curb your team\u2019s attitude and behavior when it comes to working differently.<\/p>\n In general, all project management tools should promote collaboration, open communication, and task management.<\/p>\n However, Agile project management tools get even more specific. They excel in managing workflows centered around multiple review processes. Also, because you\u2019ll need to better adapt to changing tasks or priorities, suitable tools allow you to move these things around quickly and effortlessly (think drag and drop rather than re-inputting).<\/p>\n Some popular Agile project management tools you can get started with are:<\/p>\n Monday.com Asana Trello Nifty With most of these tools, there are additional add-ons you could get to further boost productivity. For instance, if you find it inconvenient to input regular changes into a virtual task board, or just want to save a bit of time, set up a virtual assistant<\/a>, which helps you keep on top of managing tasks with just your voice.<\/p>\n Or, perhaps you\u2019re waiting on critical updates from team members and don\u2019t want to keep switching back and forth between tools to check on these. You can get notified on any project updates in Asana<\/a> or Trello <\/a>while you\u2019re messaging your team members <\/a>elsewhere.<\/p>\n When you first try out these tools you might not need to explore every feature. So make sure to plan ahead in order to choose a tool that can scale to your needs. Different tools excel in different areas\u2014some are better for remote teams, others have an easier interface to work with. Find out what your team\u2019s core needs are and cater to them!<\/p>\n Your first foray into the world of Agile might receive mixed opinions.<\/p>\n Some team members may be doubtful of its benefits. Others see the benefits but are afraid of getting their own feet wet. One way to remedy this is to document EVERYTHING.<\/p>\n Every piece of learning becomes training material for future users of the Agile method. As you Create a guide that\u2019s detailed enough for you to essentially hand over to another project team looking to get started with Agile. By having a concrete set of steps outlining the tried-and-true, this eases doubt and creates confidence for others.<\/p>\n Change isn\u2019t always easy\u2014we know that, you know that, and your team knows that.<\/p>\n By trying out an Agile approach to project management using Scrum, you\u2019re going to be introducing change and possibly a bit of discomfort in the beginning.<\/p>\n But here\u2019s the good news. You\u2019re not the first one, nor are you the only one to face this.<\/p>\n Nearly 1 in 4 of the highest performing companies completed projects with Agile or a blend of Agile and traditional project management approaches<\/a>.<\/p>\n Not to mention, beyond this article, there\u2019s a sea of resources online<\/a> and in books<\/a> to reference if you ever feel lost along the way.<\/p>\n Like we said, give it a shot by choosing a small project to start with in order to prove out the advantages for your business. Once you gain momentum with it, scale up at a pace that works for you.<\/p>\n With a couple successes under your belt, you\u2019ll likely notice a shift in overall project efficiencies. Not to mention, a positive shift in the mindset of your team so their work is collaborative, autonomous, and empowered.<\/p>\n","protected":false},"excerpt":{"rendered":" Imagine this. You and three friends have a big task ahead of you. Let\u2019s say it\u2019s preparing Thanksgiving dinner. Dominic designates himself as the dessert expert and starts kneading the dough. Nadya brought the bird, so she\u2019s off preparing that. In the other room, Ming\u2019s crafting cocktails while Daniel, not aware that Dominic\u2019s making the …<\/p>\n","protected":false},"author":29,"featured_media":41708,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[17901],"tags":[18127,18128,8251,18129],"class_list":["post-41696","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-business-leadership","tag-agile","tag-agile-project-management","tag-project-management","tag-scrum"],"acf":[],"yoast_head":"\nDemystifying \u201cAgile\u201d and \u201cScrum\u201d<\/h2>\n
What is Agile?<\/h3>\n
What is Scrum?<\/h3>\n
\n
So, what\u2019s the difference between Agile and Scrum?<\/h3>\n
\n<\/a><\/p>\n5 steps of the Scrum framework<\/h2>\n
\n
![\"Scrum](\"\/us\/en\/blog\/wp-content\/uploads\/2020\/07\/image5-58.png\")
<\/p>\n1. Product backlog<\/h3>\n
2. Sprint planning<\/h3>\n
![\"Sprint](\"\/us\/en\/blog\/wp-content\/uploads\/2020\/07\/image8-34.png\")
<\/p>\n
\n![\"Message,](\"\/us\/en\/blog\/wp-content\/uploads\/2020\/07\/image1-116.png\")
<\/a><\/p>\n<\/div>\n3. Sprint backlog<\/h3>\n
4. Daily scrum<\/h3>\n
5. Sprint review<\/h3>\n
\n<\/a><\/p>\nGetting started with Scrum<\/h2>\n
![\"Sprint](\"\/us\/en\/blog\/wp-content\/uploads\/2020\/07\/image3-78.png\")
<\/a><\/p>\n![\"Editorial](\"\/us\/en\/blog\/wp-content\/uploads\/2020\/07\/image2-99.png\")
<\/p>\n![\"Physical](\"\/us\/en\/blog\/wp-content\/uploads\/2020\/07\/image10-20.png\")
<\/p>\n
\n<\/a><\/p>\nWhy choose Agile project management?<\/h2>\n
\n
\nGuess where the target will move to > Set up aim > Launch > Hope that the arrow hits the center<\/em><\/li>\n
\nSet up aim > Step the left > Adjust aim > Set up aim > Step to the left > Adjust aim > Set up aim > Step to the right > Adjust aim > Launch > Hit the center<\/em><\/li>\n<\/ol>\n
\n<\/a><\/p>\n4 easy ways to get started with Agile project management<\/h2>\n
1. Choose the right project to try Agile<\/h3>\n
\n
2. Organize your team<\/h3>\n
![\"RingCentral](\"\/us\/en\/blog\/wp-content\/uploads\/2020\/07\/image6-45.png\")
<\/a><\/p>\n3. Decide on project management tools<\/h3>\n
\n<\/a>With monday.com, enjoy working in a way that suits your Agile needs while still keeping remote teams closely aligned and highly empowered.<\/em><\/p>\n![\"Agile](\"\/us\/en\/blog\/wp-content\/uploads\/2020\/07\/image7-40.png\")
<\/p>\n
\n<\/a>Asana helps you plan, organize, and manage Agile projects in a tool that’s as flexible and collaborative as your team. From start to finish, Asana has the features your team needs\u2014from boards to timelines and custom fields to dependencies\u2014to build fast and ship often.<\/em><\/p>\n![\"Agile](\"\/us\/en\/blog\/wp-content\/uploads\/2020\/07\/image4-72.png\")
<\/p>\n
\n<\/a>Trello\u2019s boards, lists, and cards enable you to organize and prioritize your projects in a fun, flexible, and rewarding way.<\/em><\/p>\n![\"Agile](\"\/us\/en\/blog\/wp-content\/uploads\/2020\/07\/image9-25.png\")
<\/p>\n
\n<\/a>Manage projects, work, and communications from home. Nifty is the collaboration hub that makes timelines, tasks, and workloads clear to your team and clients.<\/em><\/p>\n![\"Agile](\"\/us\/en\/blog\/wp-content\/uploads\/2020\/07\/image11-15.png\")
<\/p>\n4. Document your process<\/h3>\n
\nlearn and go, write down:<\/p>\n\n
The rundown on Agile project management with Scrum<\/h2>\n