Guide: Project Management - Agile Methodologies
Description
Developing software in a team can be a very complex task, given the different types of personalities, skills and interests involved. Traditionally, a software project was centralized in the Project Manager, a professional specialized in creating a plan and orchestrating a team to execute it. But, more often than not, this process proved inadequate to the software industry due to the long cycles of development and problems that arose from not trying out the features more quickly.
From this context, teams increasingly adopted Agile Development Methodologies such as Scrum and Kanban, which count on short development iterations (i.e. shipping code often). In this Guide you will learn about these methodologies and how they can help out on the group works during the course and in your professional career.
Knowledge
- Understand what is project management
- Understand what is Agile Development
- Understand what is Scrum and its components
- Understand what is Kanban and its components
Skills
- Be able to write an article
Topics
- Traditional/Waterfall vs Agile
- Scrum
- Roles
- Product Owner
- Product Backlog
- Scrum master
- Team
- Product Owner
- Ceremonies
- Sprint planning
- Sprint Backlog
- User Stories
- Points
- Velocity
- Daily Scrum
- Stand-up meeting
- Burn-down Charts
- Retro tools
- Conflict resolution
- Sprint planning
- Definition of done
- Roles
- Kanban
- Kanban board
- Kanban cards
- Work-in-progress (WIP) limits
Action Points
- Read-up on Project Management in Software Development as a whole
- Learn about Scrum and Kanban, making sure to understand all topics listed in the Guide
Deliverable: Technical Article
- Submit:
- Article’s public URL
- Minimum requirements:
- Technical article about Agile Development
- Possible to pick a specific topic to talk about in details instead of something more generic