How to deliver software quickly and continuously
Developing software is not an easy task, it involves a lot of knowledge, countless skills, and besides that we are still talking about something difficult to measure and tangible, unless it is built. In the software industry we have several techniques and approaches that are used to solve this "problem", it would be one more characteristic of software development. Here at Idopter Labs the approach used to reduce the impacts of the difficulty of measuring and tangibilizing what is going to be developed is delivering software fast and continuously. This post has 5 tips on how to do this and why this way your chances of success can be greater.
PBB straight from the Trenches
Idealized and defined by the agile product specialist Fábio Aguiar, PBB - Product Backlog Building, is a technique that facilitates and simplifies the creation and refinement of an effective and emerging backlog for software development in agile teams. For some years now I have been working as Product Owner (PO) at Idopter Labs and I would like to use my experience to comment, in this article, about two valuable points of my day-to-day life where PBB facilitates and helps me a lot.
The Ultimate Software Project Workflow
Having worked on a multitude of software projects in the past 10 years, our team has adopted a workflow which we believe allows us to achieve peak efficiency. By following this workflow we are able to continuously deliver value to our clients, starting on the very first week of work.The workflow is simple. It's composed of two phases: Inception and Development.This is the first of a series of posts where I will describe these two phases, along with a few important practices we use on each of them.In this post, I will describe the first phase, Inception. Albeit being the less technical of the two phases, we strongly believe this is the most productive way to gather requirements and, most importantly, collectively build a vision for the project.
