How to easily apply Agile Project Managament & Scrum to your Startup
If you are launching a new sotware product with your startup, probably the best way to mange your project is Agile. Agile is a great methodology because give you the chance to easily adapt planning, development and improvement, that is great for a startup environemnt where pivoting could be a must. This framework is composed by a lot of techniques and tools, where the main ones are Scrum and Sprint.
In this post I would like to show to you how to easily adapt this technique to manage your development software project and apply agile techniques without being a certified project manger and in particular become crazy or wasting time.
The Product Owner create together with stakeholders a Product Backlog. The Product Backlog is made by an ordered list of requirements that a Team maintains for final product. It consists of features, bug fixes, non-function requirements, requirements, or everything is necessary to create and deliver the final product.
A Product Backlog is composed by Items (PBI – Product Backlog Items) that are afterwards ordered by the Developement Team depending on business considerations or better by dependency, risks, value and date needed.
Phase 2 – Cycle
Starting from the PBI, through prioritizations, create the Sprint Backlog. The Sprint Backlog is the list of work the Development Team must complete during the next Sprint time. The list is filled until the Development Team feels it has enough work.The Development Team should keep in mind its past performance and overall the delivery time for the complete product.
A Sprint phase is usually one week, but it could be more if you want. Anyway it should never last more than 4 weeks, otherwise your project is out of control. I kindly suggest to you to start with one week and ligthly adapt.
Every day the team should meet each other in order to review the status of the current sprint backlog and react.
Sprint Backlog1 Example
Sprint Backlog2 Example
Once a Sprint has been delivered, the Product Backlog Items are reviewed, analyzed and reprioritized if necessary. The next set of functionality is selected for the next Sprint until all Product Backlogs Items are completed
The increment is the sum of all the Product Backlog Items completed during a Sprint and all previous Sprints. At the end of a Sprint, the increment must be complete and in a usable condition, as the Product Owner could decide to release it.
Also if this post is an introduction to the complete Agile framework, and in particular to Scrum, you could easily start in order to understand how to use it, or to understand if it fit to your team. In a second time go deep by reading the below books:
- Scrum: The Art of Doing Twice the Work in Half the Time
- Scrum: a Breathtakingly Brief and Agile Introduction