Tag Archives: Scrum

Agile Coaches at //SEIBERT/MEDIA – Company Level Tasks Part I: Education & Training

Agile article image

We want to use our capabilities and strengths to achieve the greatest positive impact on our company and add value to our teams. Our work has moved more and more from the team level to the corporate level. As Agile Coaches, company training and further education is important. But first, here is some food for thought at a more abstract level.

Codeyard: Helping You Achieve a Successful Software Development Process

Codeyard introduction by Martin Seibert

Codeyard is our new product suite, specially developed for companies planning larger or very large software projects. It is a product suite of software programs and expert services, which provide both the technical and procedural infrastructure necessary to achieve a seamless and structured development workflow. We offer Codeyard as a professional and powerful solution for quickly setting up and integrating a tailored, effective and efficient software development process, from concept to delivered product.

Convinced about self-organized teams

Agile tag cloud

When we started building websites professionally in 1996, we were still operating on intuition. Meticulous project planning was foreign to us. The business developed, we grew and quickly reached a point where we began looking for professional processes for developing our projects. We tried several (Gantt-Charts with MS Project and project checklists we developed ourselves), but none had the result we hoped for. For a while, project managers could decide how they wanted to develop their projects.

Codeyard Building Blocks – Atlassian’s HipChat, Confluence, JIRA, Bitbucket and Bamboo together

Codeyard is our all-in-one-project solution for every Atlassian tool installed, configured and heavily used with your employees. It is a concept to launch approach that most product and service companies need to offer their customers to create value. Let’s talk about the Atlassian tool stack and how users can use it as a holistic solution to delivering value to customers (with or without software).

99 Reasons for Scrum: How service providers benefit from Scrum projects

We have discussed the Scrum framework in software development in various of our blogs and in our wiki. The conclusion has always been: it is not an easy task to establish agile methods, however, Scrum is always worth it. In this series of articles, we have collected 99 reasons, why customers, coworkers, and service provider equally benefit from Scrum. In the last two articles, we explored how the customers and how staff benefits from Scrum. The last article lists the benefits of Scrum projects for service providers:

99 Reasons for Scrum: How staff benefits from Scrum projects

We have discussed the Scrum framework in software development in various of our blogs and in our wiki. The conclusion has always been: it is not an easy task to establish agile methods, however, Scrum is always worth it. In this series of articles, we have collected 99 reasons, why customers, coworkers, and service provider equally benefit from Scrum. In the last article, we explored how the customers benefit. This article focuses on the benefits of Scrum projects for staff:

99 Reasons for Scrum: How customers benefit from Scrum projects

We have discussed the Scrum framework in software development in various of our blogs and in our wiki. The conclusion has always been: it is not an easy task to establish agile methods, however, Scrum is always worth it. In this series of articles, we have collected 99 reasons, why customers, coworkers, and service provider equally benefit from Scrum. First, let’s take a look at the benefits for the customer:

There’s life in paper yet: The InstaPrinta prints customized JIRA tickets for analog boards

The paper-less office was meant to banish all paper from the office. In agile teams, however, this does not apply and this is where InstaPrinta comes in. Admittedly, a tool like Atlassian’s JIRA is a great way to manage tasks. However, in day-to-day work, a digital Agile Board in JIRA does not have the same presence as a large magnet board right in the center a team office that is full of task notes. At a glance, every team member knows what needs to be done and who is working on what. Furthermore, the magnet board contains numerous additional sections like an improvement board, a skill matrix, an absence calendar and more. This makes the analog board the central “cockpit” for all information relevant to the teams.