We are often contacted by customers with very rough, technical requirements lists for software projects. In cases like this, the first project step for //SEIBERT/MEDIA is to turn the customer’s requirements list into a product backlog that highlights how the customer benefits from the requirements. This is not a trivial task and requires time and resources. But why should the customer pay for this preparation work that has nothing to do with actually completing the project?
We’ve been using the agile framework Scrum to complete software development projects for almost four years now. Many Scrum elements also form the basis of our process model for continuously improving our organization. The internal label for our process is “Agile Org”. In one-month cycles, we think about things we want to change and work on them. The topics vary greatly from improving company strategy and forming more intensive customer relationships to internal issues like creating a good work-life balance.
In many teams, islands of knowledge are a major topic and great challenge. At the same time, team members ask themselves what areas they should continue improving and training in. This is where a “skill matrix” can provide a starting point for exchange within development teams. This aid helps you process and visualize:
The JIRA plugin Tempo Planner offers agile capacity and resource scheduling, team and project management, and business data for teams. It extends the JIRA platform by deeper agile planning and management specific features.