For this assignment, you will choose one of the project management techniques described below (Kanban, Scrum, or Scrum-Ban) and use GitHub Project to manage your project according to that methodology. You will work in a team to create a GitHub Project board that reflects your chosen methodology, and use it to manage your team’s workflow and track progress on a project of your choice.
Your team’s GitHub Project board should be actively used and maintained throughout the duration of the assignment. You should update the board regularly to reflect the current state of your project, and use it as a central hub for tracking progress, assigning tasks, and communicating with your team members.
At the end of the assignment, you will create a presentation that explains why your team chose the project management methodology. Your report should explain what you can improve in the next sprint and have any measurable indicators that you can use to judge if your improvements result in improvements to your teams efficiency or product quality.
Create a table in a markdown file on your repository and share it with your team. Add columns for issue title,story points, issue link, status, assigned to, assigned on, completed on, category, status notes. Each time a team member completes a task in the project they need to create an issue on GitHub and add that link to this document. Tasks can be the following categories: Feature, Bug, Docs, or Devops Task
Please submit your document to Canvas
Rubric for Project Management Assignment
Total Points: 20
| Criteria | Not Complete | Complete | Exceeds Expectations |
|---|---|---|---|
| Project Management Board reflects methodology chosen | 0 | 1 | 2 |
| Columns on board match workflow of project | 0 | 1 | 2 |
| Tasks added and assigned to team members | 0 | 1 | 2 |
| Regular updates to board to reflect project progress | 0 | 1 | 2 |
| Effective use of GitHub features to communicate | 0 | 1 | 2 |
| Presentation: Introduction to chosen methodology | 0 | 1 | 2 |
| Presentation: Productivity rating for each team member | 0 | 1 | 2 |
| Presentation: Team member learning and improvement | 0 | 1 | 2 |
| Presentation: Links to project task board and queue | 0 | 1 | 2 |
| Presentation: Link to productivity task log file | 0 | 1 | 2 |
| Productivity log table with required columns | 0 | 1 | 2 |
As the CEO of MyWebClass.org, I have a goal of combining the best of Lean and Agile methodologies to develop our products in the most efficient and effective way possible. One of the key principles of Lean is the idea of a pull process, where the focus is on delivering value to the customer based on their needs and preferences, rather than pushing out products based on what we think they want. By adopting a pull process, we can ensure that we’re creating products that meet our customers’ needs and provide maximum value.
At the same time, the Agile Manifesto is an important philosophy that emphasizes flexibility, collaboration, and continuous improvement. However, it’s important to recognize that there are many different implementations of Agile, and not all of them will be the right fit for our team. That’s why we need to carefully consider the different Agile methodologies out there, like Scrum, Kanban, and Scrumban, and choose the one that best aligns with our goals and values.
Ultimately, our goal is to create a culture of continuous improvement, where we’re always looking for ways to work more efficiently, create more value, and better serve our customers. By adopting the best practices of Lean and Agile, we can achieve this goal and take our products to the next level.
Kanban is a project management methodology that emphasizes visualizing work and limiting work in progress to improve efficiency and throughput. The basic idea of Kanban is to use a physical or digital board to track the status of tasks or work items, with columns representing different stages of the workflow. Teams using Kanban typically focus on optimizing flow, minimizing bottlenecks, and continuously improving their process.
Minimum requirements: A physical or digital board, such as a whiteboard, sticky notes, or a Kanban software tool.
General process: Create a board that reflects your workflow and current state of work, add work items or tasks to the board, and track progress through the workflow stages.
Scrum is an agile methodology that emphasizes iterative development and teamwork. Scrum is designed to help teams deliver high-quality products by focusing on collaboration, transparency, and continuous improvement. The key features of Scrum include sprint planning, daily stand-up meetings, sprint reviews, and retrospectives.
Minimum requirements: A product backlog, a sprint backlog, a sprint planning meeting, daily stand-up meetings, and a sprint review.
General process: Create a product backlog of features or user stories, prioritize the backlog items, select items for the next sprint during the sprint planning meeting, hold daily stand-up meetings to track progress, conduct a sprint review at the end of the sprint, and hold a retrospective to identify areas for improvement.
Scrumban is a hybrid of Kanban and Scrum that combines the best of both methodologies. Scrumban aims to improve the flexibility and flow of Kanban while retaining the structure and teamwork of Scrum. Teams using Scrumban typically focus on continuous improvement, limiting work in progress, and optimizing flow.
Minimum requirements: A physical or digital board, a product backlog, a sprint backlog, a sprint planning meeting, daily stand-up meetings, a sprint review, and a retrospective.
General process: Create a product backlog of features or user stories, prioritize the backlog items, select items for the next sprint during the sprint planning meeting, hold daily stand-up meetings to track progress, conduct a sprint review at the end of the sprint, and hold a retrospective to identify areas for improvement. Use a Kanban board to visualize work and track progress through the workflow stages.