DS103-Metrics-and-Data-Processing/DS103PM-L4-Kanban.ipynb

{
 "cells": [
  {
   "cell_type": "markdown",
   "id": "50e6ddbb-52d3-4a02-9b69-100a4181e3b0",
   "metadata": {},
   "source": [
    "# DS103 Agile Project Management : Lesson Four Kanban"
   ]
  },
  {
   "cell_type": "markdown",
   "id": "d1bd4bfc-9b15-4b80-87b4-b8b60eb56371",
   "metadata": {},
   "source": [
    "### Table of Contents <a class=\"anchor\" id=\"DS103L9_toc\"></a>\n",
    "\n",
    "* [Table of Contents](#DS103L9_toc)\n",
    "    * [Page 1 - Overview](#DS103L9_page_1)\n",
    "    * [Page 2 - Kanban History](#DS103L9_page_2)\n",
    "    * [Page 3 - Kanban Workflow](#DS103L9_page_3)\n",
    "    * [Page 4 - Kanban Benefits](#DS103L9_page_4)\n",
    "    * [Page 5 - Kanban Common Challenges](#DS103L9_page_5)\n",
    "    * [Page 6 - Key Terms ](#DS103L9_page_6)\n",
    "    * [Page 7 - Hands-On](#DS103L9_page_7)\n",
    "\n",
    "    "
   ]
  },
  {
   "cell_type": "markdown",
   "id": "ef5a8c65-ed48-4354-a257-e01b0fd733d4",
   "metadata": {},
   "source": [
    "<hr style=\"height:10px;border-width:0;color:gray;background-color:gray\">\n",
    "\n",
    "# Page 1 - Overview of this Module<a class=\"anchor\" id=\"DS103L9_page_1\"></a>\n",
    "\n",
    "[Back to Top](#DS103L9_toc)\n",
    "\n",
    "<hr style=\"height:10px;border-width:0;color:gray;background-color:gray\">"
   ]
  },
  {
   "cell_type": "code",
   "execution_count": 2,
   "id": "9f608461-2ce8-403c-8516-7bd97e05ec42",
   "metadata": {},
   "outputs": [
    {
     "data": {
      "text/html": [
       "\n",
       "        <iframe\n",
       "            width=\"720\"\n",
       "            height=\"480\"\n",
       "            src=\"https://player.vimeo.com/video/219153333\"\n",
       "            frameborder=\"0\"\n",
       "            allowfullscreen\n",
       "        ></iframe>\n",
       "        "
      ],
      "text/plain": [
       "<IPython.lib.display.VimeoVideo at 0x7ffcc8259b80>"
      ]
     },
     "execution_count": 2,
     "metadata": {},
     "output_type": "execute_result"
    }
   ],
   "source": [
    "from IPython.display import VimeoVideo\n",
    "# Tutorial Video Name: Kanban\n",
    "VimeoVideo('219153333', width=720, height=480)"
   ]
  },
  {
   "cell_type": "markdown",
   "id": "5b6ad526-95fa-43c4-bc43-1fe807708ed3",
   "metadata": {},
   "source": [
    "# Overview\n",
    "\n",
    "Kanban is another project, or process, management framework which aligns well with the principles of Agile Software Development.  Whereas Scrum has an emphasis on short, measured increments of shippable functionality, Kanban provides a continual stream of production with a focus on reducing waste by only delivering what is desired by the customer.  Kanban is often implemented as a modification of Scrum, adding influence over the workflow, but borrowing concepts like daily standup and User Story structure."
   ]
  },
  {
   "cell_type": "markdown",
   "id": "7990ac7a-5a2f-4744-af14-1b7e385ea484",
   "metadata": {},
   "source": [
    "<hr style=\"height:10px;border-width:0;color:gray;background-color:gray\">\n",
    "\n",
    "# Page 2 - Kanban History<a class=\"anchor\" id=\"DS103L9_page_2\"></a>\n",
    "\n",
    "[Back to Top](#DS103L9_toc)\n",
    "\n",
    "<hr style=\"height:10px;border-width:0;color:gray;background-color:gray\">\n"
   ]
  },
  {
   "cell_type": "markdown",
   "id": "612429df-e4ef-4d85-8460-5bc8914079c3",
   "metadata": {},
   "source": [
    "# History\n",
    "\n",
    "Remember that Scrum was highly influenced by the Lean Manufacturing processes established at Toyota?  Well, Kanban too was a product of Toyota's leadership in efficiency.  The Kanban process preceded Scrum and was established to reduce waste and minimize costly inventory for manufacturing.  The premise was simple; only build what is needed at the time of demand.\n",
    "\n",
    "Toyota's inspiration came from the retail industry, where direct-to-consumer businesses had already established an impressive system of efficient production.\n",
    "\n",
    "Consider when you go to a local store to purchase a product.  The store (hopefully) has your desired product in stock.  When you purchase the product, their stock reduces, and they notify the vendor that they need to purchase additional stock to replenish their shelves.  Meanwhile, the vendor (hopefully) has the materials required to create the product.  Once the product is made, they inform their materials vendor that they need additional materials.  This chain continues, with each down-stream *customer* informing the upstream vendor when their services are needed.\n",
    "\n",
    "At the time, Toyota was challenged by skyrocketing inventory costs and was forecasting the demand for a vehicle, and producing the components.  Often, they would miscalculate the demand, overproducing expensive parts.  Additionally, having a large number of parts stored in warehouses was incredibly expensive.\n",
    "\n",
    "So, Toyota set out to create a process which models the retail format of *just-in-time* delivery to meet the downstream demand.  They referred to this method as Kanban, which has been widely adopted by software teams today.\n",
    "\n",
    "---\n",
    "\n",
    "## Four Pillars of Kanban\n",
    "\n",
    "Kanban is a method for managing the creation of products with an emphasis on regular delivery while not overburdening the development team.  There are four simple principles to Kanban:\n",
    "\n",
    "---\n",
    "\n",
    "#### Visualize What You Do Today\n",
    "\n",
    "Similar to Scrum's notion of transparency, Kanban enforces that the team has readily available reporting to provide visuals that describe the team's progress and bottlenecks.\n",
    "\n",
    "#### Limit the Work-In-Progress\n",
    "\n",
    "Instead of regularly-paced increments, Kanban employs a continuous delivery approach.  When work is completed, and valuable functionality is customer-ready, why wait to deliver it?  Limiting the work in progress helps the team to avoid over-committing on what can be delivered and quickly identifies bottlenecks.\n",
    "\n",
    "#### Enhance Flow\n",
    "\n",
    "To facilitate continuous delivery, the team's sole focus is on completing the work in progress, after which they will begin work on the next highest priority item in the backlog.  Flow refers to the pace at which work flows through the team's workflow pipeline.\n",
    "\n",
    "#### Continuous Improvement\n",
    "\n",
    "Kanban promotes an emphasis on continuous improvement.  By leveraging the visual nature of a Kanban system, you should strive to improve your efficiencies through a constant re-evaluation of your processes.  This method should be adaptive and closely monitored for opportunities for the team to improve.\n",
    "\n",
    "---\n",
    "\n",
    "## Kanban vs. Scrum\n",
    "\n",
    "With transparency at the core of the Scrum framework, its crucial that the team builds trust and an ability to share, critique and constructively challenge each other.\n",
    "\n",
    "<table style=\"border: 1px solid black; margin: 10px\">\n",
    "    <tr>\n",
    "        <td style=\"padding: 10px;\"><strong>Kanban</strong></td>\n",
    "        <td style=\"padding: 10px;\"><strong>Scrum</strong></td>\n",
    "    </tr>\n",
    "    <tr>\n",
    "        <td style=\"padding: 10px;\">No prescribed roles</td>\n",
    "        <td style=\"padding: 10px;\">Pre-defined roles of Scrum master, Product owner and team member</td>\n",
    "    </tr>\n",
    "    <tr>\n",
    "        <td style=\"padding: 10px;\">Continuous Delivery</td>\n",
    "        <td style=\"padding: 10px;\">Timeboxed sprints</td>\n",
    "    </tr>\n",
    "    <tr>\n",
    "        <td style=\"padding: 10px;\">Work is pulled through the system (single piece flow)</td>\n",
    "        <td style=\"padding: 10px;\">Work is pulled through the system in batches (the sprint backlog)</td>\n",
    "    </tr>\n",
    "    <tr>\n",
    "        <td style=\"padding: 10px;\">Changes can be made at any time</td>\n",
    "        <td style=\"padding: 10px;\">No changes allowed mid-sprint</td>\n",
    "    </tr>\n",
    "    <tr>\n",
    "        <td style=\"padding: 10px;\">Cycle time</td>\n",
    "        <td style=\"padding: 10px;\">Velocity</td>\n",
    "    </tr>\n",
    "    <tr>\n",
    "        <td style=\"padding: 10px;\">More appropriate in operational environments with a high degree of variability in priority</td>\n",
    "        <td style=\"padding: 10px;\">More appropriate in situations where work can be prioritized in batches that can be left alone</td>\n",
    "    </tr>\n",
    "</table>\n",
    "\n",
    "Next, you will dive deeper into the specifics of how the Kanban method can help your team.\n",
    "\n",
    "---\n"
   ]
  },
  {
   "cell_type": "markdown",
   "id": "832358fd-55fa-420a-8aa2-46fbf2097986",
   "metadata": {},
   "source": [
    "<hr style=\"height:10px;border-width:0;color:gray;background-color:gray\">\n",
    "\n",
    "# Page 3 - Kanban Workflow<a class=\"anchor\" id=\"DS103L9_page_3\"></a>\n",
    "\n",
    "[Back to Top](#DS103L9_toc)\n",
    "\n",
    "<hr style=\"height:10px;border-width:0;color:gray;background-color:gray\">\n"
   ]
  },
  {
   "cell_type": "markdown",
   "id": "f564e3e7-3a7f-4936-b3a3-2e0a9ab78512",
   "metadata": {},
   "source": [
    "\n",
    "# Kanban Workflow\n",
    "\n",
    "In Software Development, Kanban is often adopted as an extension or a modification to Scrum processes.  Kanban has a much less opinionated approach to software project management.  Limiting WIP, continuous delivery and Flow are at the heart of Kanban. However, many other concepts such as the roles and ceremonies are open to the team's discretion.  In this lesson, you will explore the specifics of a Kanban workflow.\n",
    "\n",
    "---\n",
    "\n",
    "## Kanban Boards\n",
    "\n",
    "Much like a scrum board, Kanban work is visualized on a Kanban board, a tool used to visualize work and optimize the flow of the work among the team. The implementation and tooling of a Kanban board vary from team to team.  As with Scrum, some teams like the tangible sticky notes, while others prefer a more sophisticated software system for tracking their progress.\n",
    "\n",
    "The function of the Kanban board is to ensure the team's work is visual and available, their workflow is apparent, and all impediments are quickly identified. A basic Kanban Board will typically have three standard swim lanes:\n",
    "\n",
    "<table style=\"border: 1px solid black; margin: 10px\">\n",
    "    <tr>\n",
    "        <td style=\"padding: 10px;\"><strong>To Do</strong></td>\n",
    "        <td style=\"padding: 10px;\"><strong>Doing</strong></td>\n",
    "        <td style=\"padding: 10px;\"><strong>Done</strong></td>\n",
    "    </tr>\n",
    "</table>\n",
    "\n",
    "Many teams will expand on these three categories and add additional states. Notably, the *Doing* category is subject to being broken into multiple stages.  As long as the workflow and policies are clearly stated, the team should modify the swim lanes to suit their needs.\n",
    "\n",
    "It is important to note that the Kanban board serves as the source of truth for the state of the workflow.  It is imperative that team members keep the board current, so the rest of the team members have full and current visibility to the progress of the team.\n",
    "\n",
    "![Team Kanban Board. A virtual bulletin board with columns headed To do, in progress, code review, and done. Under each heading are pictures of the team members assigned to each task along with a short description of the task. It gives the option to filter by critical partners, only my partners, or recently updated.](media/kanban.png \"Kanban\")\n",
    "\n",
    "---\n",
    "\n",
    "## Kanban Cards\n",
    "\n",
    "In manufacturing, Kanban cards were implemented as a visual cue to the upstream vendor, indicating the needs of the downstream customer.  These physical cards would document the specific needs and would be handed to the vendor.  Software has adopted this format to suit your needs, and often Kanban Cards will resemble User Stories, with a familiar format:\n",
    "\n",
    "![Kanban cards. A virtual sticky note that has places for an Item ID numberm, due date, level of effort, Blank lines to complete the sentence as a blank, I want to blank, title, date accepted and date started.](media/kanbancard.png \"KanbanCard\")\n",
    "\n",
    "The Kanban board will list all required work as Kanban Cards, explicitly stating the needs of the requester (customer).  The cards will originate in the backlog, and move through the workflow based on priority and Flow.\n",
    "\n",
    "The reason for using this card format is to ensure visibility to work being done.  Recall that the first of your three Kanban pillars was to *visualize the work you do today*.  Documenting that work and placing it on a visual board helps you to understand:\n",
    "\n",
    "* What is being requested\n",
    "* What stage of the workflow is it in\n",
    "* Details of the request\n",
    "\n",
    "---\n",
    "\n"
   ]
  },
  {
   "cell_type": "markdown",
   "id": "bb1aade2-59af-4cbc-b5ed-da31e39f266d",
   "metadata": {},
   "source": [
    "<hr style=\"height:10px;border-width:0;color:gray;background-color:gray\">\n",
    "\n",
    "# Page 4 - Kanban Benefits<a class=\"anchor\" id=\"DS103L9_page_4\"></a>\n",
    "\n",
    "[Back to Top](#DS103L9_toc)\n",
    "\n",
    "<hr style=\"height:10px;border-width:0;color:gray;background-color:gray\">\n"
   ]
  },
  {
   "cell_type": "markdown",
   "id": "eba2ed6e-98dd-43f7-8761-6ecc9a13af08",
   "metadata": {},
   "source": [
    "\n",
    "# Kanban Benefits\n",
    "\n",
    "Kanban is growing in popularity among teams who are motivated to streamline their development and deployment cycle.  A Kanban workflow reduces the pressure on *launch days* by focusing on continuous delivery.\n",
    "\n",
    "By implementing the Kanban method, software teams strive to achieve the most minimal time-to-value ratio possible.  Time to face it, stakeholders are generally impatient, and many companies have overcome this impatience by employing a Kanban workflow and a continuous deployment system.  At its core, Kanban is incredibly simple; finish a task before moving on, keep your work organized, and deliver functionality as soon as it is ready.\n",
    "\n",
    "Often, the requirements passed down from stakeholders change frequently.  By *timeboxing* your efforts, you often find yourself telling stakeholders to wait until the next sprint or release cycle.  With Kanban, if the request is urgent enough, it could be the next work-in-progress as soon as you make room in the queue.\n",
    "\n",
    "By restricting the Work-In-Progress, you immediately identify bottlenecks and skill gaps.  If a team member is available for new work, but the *in progress* lane is already full based on your work-in-progress limits, you will immediately gain insight into how you can optimize.  Perhaps you need more training on a particular skill to move items along the flow, or perhaps there is a broken system which is preventing a card from moving.\n",
    "\n",
    "A few of the benefits of Kanban:\n",
    "\n",
    "* Because it focuses on continuous improvement, it's likely that teams will continually yield high-quality results.\n",
    "* Due to the focus on continuous improvement, both productivity and efficiency are likely to increase while reducing wasted time and resources.\n",
    "* Goals can be more easily accomplished by Teams due to the visual nature of Kanban boards or cards.\n",
    "* The decrease in waste leads to a higher-quality product or service at a cost-effective price for the consumer.\n",
    "\n",
    "Kanban is not as rigid as most of the other methodologies. There are no set times for tasks, and priorities can continuously be reassessed. By delivering small portions of the project to the end user continuously, the project team has many opportunities to fix their mistakes and give the user what they want based on feedback. In this way, the user's needs are met to maximum effect.  Kanban also minimizes wasted work and maximizes the related measures of productivity and efficiency. By wasted work in the context of software development, you mean work that is not needed, incorrect, or not valued.\n",
    "\n",
    "---\n"
   ]
  },
  {
   "cell_type": "markdown",
   "id": "ead4ad3c-2fe6-457e-8924-1410e951bebd",
   "metadata": {},
   "source": [
    "<hr style=\"height:10px;border-width:0;color:gray;background-color:gray\">\n",
    "\n",
    "# Page 5 - Kanban Common Challenges<a class=\"anchor\" id=\"DS103L9_page_5\"></a>\n",
    "\n",
    "[Back to Top](#DS103L9_toc)\n",
    "\n",
    "<hr style=\"height:10px;border-width:0;color:gray;background-color:gray\">\n"
   ]
  },
  {
   "cell_type": "markdown",
   "id": "bbbc06a2-e702-47a1-942f-cbcbe31221a7",
   "metadata": {},
   "source": [
    "# Kanban Common Challenges\n",
    "\n",
    "Kanban, although highly regarded, is not without its challenges as well. In this lesson, you will explore some of the common challenges that teams face when implementing a Kanban workflow.\n",
    "\n",
    "---\n",
    "\n",
    "## Estimation\n",
    "\n",
    "The purpose of story pointing in a _Scrum_ setting is to establish a velocity accurately. In a Kanban workflow, however, there is no concept of a sprint, therefore, no velocity. Kanban teams instead typically measure _Flow_ or the _Flow Rate_ as either the sum of story points in a given time-period or a ticket quantity.\n",
    "\n",
    "Consider a scenario where you were to measure productivity as ticket volume. In this case, having equally-sized tickets would be essential to accurate metrics. For this reason, Kanban is often seen as a preferred methodology to teams which are tasked with maintaining an existing system. The measurement here is more historical than predictive.\n",
    "\n",
    "Kanban can, at times, be more challenging to predict delivery of features.\n",
    "\n",
    "---\n",
    "\n",
    "## Throttling Work in Progress\n",
    "\n",
    "Without a Sprint structure, Kanban teams rely on limiting work in progress to throttle the flow of cards (stories). This can be a challenging concept to calibrate with a new team and can take time and revision to get to a proper setup.\n",
    "\n",
    "The WIP limits help to protect the team by establishing manageable rates of throughput for tickets. In Scrum, the sprint planning meeting helps prevent overwhelming the team, as the team has an established velocity and a chance to voice concerns about the sprint backlog. In Kanban, the WIP limit is the only mechanism in place to curb product owner expectations and enable the team to have a healthy balance.\n",
    "\n",
    "---\n",
    "\n",
    "## Unified Backlog\n",
    "\n",
    "Sprint backlogs don't exist on a Kanban team since there is no concept of a sprint. Instead, the team can pull at any time, from the top of the product backlog. This requires the Product Owner to be highly involved in the day to day grooming of the product backlog. There is no opportunity for the Product owner to do a _big cleanup_ on the backlog before a sprint planning.\n",
    "\n",
    "The benefit of continuous flow is that the backlog can be much more flexible. The downside is that it requires much more effort by the product owner to keep it current.\n",
    "\n",
    "---\n",
    "\n",
    "## Be Agile First, Be Kanban Second\n",
    "\n",
    "Remember, your goal is to be an **Agile** software team. Kanban is a great workflow to achieve Agile principles. However, don't get too wrapped up in the process. Remember your ultimate goal is to be _Agile_, not to be _Kanban_.\n",
    "\n",
    "```c-lms\n",
    "topic: Extreme Programming\n",
    "```\n",
    "\n",
    "# Extreme Programming (XP)\n",
    "\n",
    "You've now learned about two of the most common Agile frameworks in Scrum and Kanban. Extreme Programming (XP) is another common Agile framework centered around engineering principles and focused on ensuring delivery of high-quality software. XP teams work collaboratively in short development cycles and are flexible and adaptable to change. XP utilizes user stories and frequent small planned releases.\n",
    "\n",
    "**XP has twelve core practices grouped into four categories:**\n",
    "\n",
    "* **Fine Scale Feedback**\n",
    "    -  Test Driven Development\n",
    "    -  Planning Game (frequent release and iteration planning)\n",
    "    -  Whole Team (the customer is a member of the team and available at all times)\n",
    "    -  Pair Programming (two people should produce code)\n",
    "* **Continuous Process**\n",
    "    -  Continuous Integration\n",
    "    -  Design Improvement (embrace refactoring)\n",
    "    -  Small Releases (deliver frequent releases of working functionality)\n",
    "* **Shared Understanding**\n",
    "    -  Simple Design\n",
    "    -  System Metaphor (class and method should be named for functionality)\n",
    "    -  Collective Code Ownership\n",
    "    -  Coding Standards (entire team agrees on standards and holds one another accountable)\n",
    "* **Programmer Welfare**\n",
    "    -  Sustainable Pace (people perform best when rested)\n",
    "\n",
    "There are many other lesser-known Agile frameworks, and even more being defined currently.  These are three of the more commonly encountered, and for the remainder of this course, you will focus on Scrum and Kanban implementations.\n",
    "\n",
    "---"
   ]
  },
  {
   "cell_type": "markdown",
   "id": "dd9e3b8a-9224-447f-8cf7-5035cae86421",
   "metadata": {},
   "source": [
    "<hr style=\"height:10px;border-width:0;color:gray;background-color:gray\">\n",
    "\n",
    "# Page 6 - Key Terms<a class=\"anchor\" id=\"DS103L9_page_6\"></a>\n",
    "\n",
    "[Back to Top](#DS103L9_toc)\n",
    "\n",
    "<hr style=\"height:10px;border-width:0;color:gray;background-color:gray\">\n"
   ]
  },
  {
   "cell_type": "markdown",
   "id": "a81e2098-28ef-4ff5-a155-afe824de4323",
   "metadata": {},
   "source": [
    "# Key Terms\n",
    "\n",
    "Below is a list and short description of the important keywords you have learned in this lesson. Please read through and go back and review any concepts you don't fully understand. Great Work!\n",
    "\n",
    "<table class=\"table table-striped\">\n",
    "    <tr>\n",
    "        <th>Keyword</th>\n",
    "        <th>Description</th>\n",
    "    </tr>\n",
    "    <tr>\n",
    "        <td style=\"font-weight: bold;\" nowrap>Kanban</td>\n",
    "        <td>A project management method with an emphasis on continual delivery and reducing waste.</td>\n",
    "    </tr>\n",
    "    <tr>\n",
    "        <td style=\"font-weight: bold;\" nowrap>Work-In-Progress (WIP)</td>\n",
    "        <td>The total of all work which is currently being done.</td>\n",
    "    </tr>\n",
    "    <tr>\n",
    "        <td style=\"font-weight: bold;\" nowrap>Flow</td>\n",
    "        <td>The throughput of work through the project management workflow.</td>\n",
    "    </tr>\n",
    "    <tr>\n",
    "        <td style=\"font-weight: bold;\" nowrap>Kanban Board</td>\n",
    "        <td>A visual representation of the Kanban project's current status.</td>\n",
    "    </tr>\n",
    "    <tr>\n",
    "        <td style=\"font-weight: bold;\" nowrap>Kanban Cards</td>\n",
    "        <td>Details and supporting documentation for work being requested.</td>\n",
    "    </tr>\n",
    "</table>\n",
    "\n"
   ]
  },
  {
   "cell_type": "markdown",
   "id": "42cb7d8a-aced-42e5-ac24-32acf8c95473",
   "metadata": {},
   "source": [
    "<hr style=\"height:10px;border-width:0;color:gray;background-color:gray\">\n",
    "\n",
    "# Page 7 - Hands-On<a class=\"anchor\" id=\"DS103L9_page_7\"></a>\n",
    "\n",
    "[Back to Top](#DS103L9_toc)\n",
    "\n",
    "<hr style=\"height:10px;border-width:0;color:gray;background-color:gray\">\n"
   ]
  },
  {
   "cell_type": "markdown",
   "id": "cf0debaf-5fae-4035-8e7d-ae62e62456cb",
   "metadata": {},
   "source": [
    "In this Hands-On Project, you will be building a Kanban board to represent the backlog and recommended workflow for a project. Through this project, you will gain experience with working in a Kanban workflow, creating Kanban cards and prioritizing them. `This Hands-On will be graded`, so be sure you complete all requirements.\n",
    "\n",
    "<div class=\"panel panel-danger\">\n",
    "    <div class=\"panel-heading\">\n",
    "        <h3 class=\"panel-title\">Caution!</h3>\n",
    "    </div>\n",
    "    <div class=\"panel-body\">\n",
    "        <p>Do not submit your project until you have completed all requirements! You will not be able to resubmit.</p>\n",
    "    </div>\n",
    "</div>\n",
    "\n",
    "---\n",
    "\n",
    "## Requirements\n",
    "\n",
    "Leveraging what you've learned about the Kanban method, you will need to create a Kanban board to represent a typical workflow for the project described below. Pay particular attention to your swim lanes, your WIP limits, and any specific policies that should be described. Populate a complete product backlog to the best of your knowledge, and ensure that anyone viewing your Kanban board can gain a quick understanding of the status of your project. Meet the below requirements:\n",
    "\n",
    "* **Create a Trello Project:** Log into your Trello account and click *Create new Board*.  You can name the project \"ABC Inc. Registration\" or a project title of your choosing.  Select \"none\" for the team and change the board setting from *private* to *public*.\n",
    "\n",
    "* **Create a Kanban Board:**\n",
    "    -  Ensure your Lists represent appropriate swim lanes for a Kanban project.\n",
    "    -  Pay particular attention to the workflow that is defined by your swim lanes; Kanban offers you more control over the workflow.\n",
    "    -  Create appropriate WIP limits for a team of 6 (4 Developers and 2 Test Engineers).\n",
    "\n",
    "* **Create a Product Backlog:** Populate your Product Backlog by adding a minimum of 10 Kanban Cards.  Each Card should represent a user story, and should follow the standard user story format: \"As a ____, I need ____ to ____.\"\n",
    "\n",
    "* **Groom your Backlog:** Reorder the stories by priority with the most urgent stories up top.  Consider the value to the customer, and ensure that the most valuable stories are at the top.\n",
    "\n",
    "---\n",
    "\n",
    "## Example Project:\n",
    "\n",
    "Feel free to plan any project you like; however, if you need inspiration for a project to design, you may use the following:\n",
    "\n",
    "* ABC Inc. (your client) is asking you to plan a project to develop a web application which will allow students to register for an upcoming class.  \n",
    "\n",
    "* They would like a student to be able to log into a web application and view available courses and then select one in which to register.  Registration will be limited based on classroom capacity.\n",
    "\n",
    "* The administration will need the ability to manage the class schedule, creating, removing, and modifying classes.\n",
    "\n",
    "* The client values quality and innovative solution over something that is quick to market.  They are looking to you and your team to help define some features that would make class registration a simple and easy process.\n",
    "\n",
    "<div class=\"panel panel-danger\">\n",
    "    <div class=\"panel-heading\">\n",
    "        <h3 class=\"panel-title\">Caution!</h3>\n",
    "    </div>\n",
    "    <div class=\"panel-body\">\n",
    "        <p>Be sure to zip and submit your entire document when finished!</p>\n",
    "    </div>\n",
    "</div>"
   ]
  }
 ],
 "metadata": {
  "kernelspec": {
   "display_name": "Python 3 (ipykernel)",
   "language": "python",
   "name": "python3"
  },
  "language_info": {
   "codemirror_mode": {
    "name": "ipython",
    "version": 3
   },
   "file_extension": ".py",
   "mimetype": "text/x-python",
   "name": "python",
   "nbconvert_exporter": "python",
   "pygments_lexer": "ipython3",
   "version": "3.9.16"
  }
 },
 "nbformat": 4,
 "nbformat_minor": 5
}