Agile Retrospectives
For your remote team to truly reach a point of iterative and incremental development using agile methodologies, you need to have the best possible agile retrospectives sessions. No way around that. Here are our reasons why the Agile Retrospectives for Jira or Agile Retros for Confluence add-ons can help your
Agile
This post inspired by Paul Goddard’s & Geoff Watts’ Post on Scrum Alliance. If you work with #Agile software development methodologies you are familiar with Agile Retrospectives: "retrospective (rèt´re-spèk-tîv) — a ritual held at the end of a project to learn from the experience and to plan changes
Agile
Agile development teams seem to appreciate the value of having standup meetings. They are easily adopted by teams. Unfortunately, I can’t say the same thing about Agile Retrospectives. One of the common problems that I’ve noticed is the lack of discipline with retrospectives, especially when it comes to
Agile Retrospectives
The key point of doing Sprint Retrospectives is helping your team to keep nourishing a continuous improvement spirit in a concrete and fast manner to effectively implement its outcomes. Retrospectives purpose, in a high-level sense, is to “plan ways to increase quality and effectiveness”, as stated on Scrum.org, and
Agile Retrospectives
Agile Retrospectives are a very helpful way to have the team reflect and discuss. It’s a safe zone for the team to point out what they’ve been doing right and what do they need to improve. We’ve talked about how to set the right mood to empower
Agile
In software development, time is a central concept, and delivering value as early as possible is a primary driver for the industry. Teams build products to save users precious time, and these tools are made in a prioritized fashion, mitigating waste. Even though many teams use Agile frameworks to successfully
Agile
An area that has been gaining a lot of attention these couple of years in Software Development is User Research. Agile User Research is an activity focused on generating insights for product owners and project managers into what drives adoption of a tool or feature. For many of us that
Agile
The problem is not your team, or the process. The problem are your outputs. Based on an article by Leon Tranter. If you are part of a software development team that uses Agile methodologies, then you know that the key to your team’s continuous improvement in the long term
Agile
This post was inspired by Mike Cohn’s: Does a Scrum Team Need a Retrospective Every Sprint? We at CatapultLabs realized that it is very often that we find a team member that either does not perceive the full value of having an Agile Retrospective session every sprint or that
Agile
Agile practices are for everyone, in every industry (yes, even if you are not in the tech industry), not just software development. Today, almost everything is made of software. If you are still holding on to old organization paradigms, you are leaving money on the table. Let CatapultLabs tell you
Tools
Once I had a job where my primary mission was to properly implement the usage of a CRM they had acquired some months ago. Would you guess which was the most challenging part? It was not to develop a functional data structure, integrate it with other platforms, or customize its
Agile
This post is dedicated to Behance founder, Scott Belsky, who worked for 10 years building the Behance design platform before selling it to Adobe. In a popular post he talks about Escape Velocity and the ups & downs of building a company. At CatapultLabs we had such an endeavor within