Trendy ideas on how to boost your Software Development cycles and detect opportunity areas.
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
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
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
Agile
Is Agile a culture or is it only just a software development thing? What makes a team a truly Agile team? Why are values important? What changes are required in order to support an Agile culture? These are the questions we are addressing in this post. Remember that CatapultLabs is
Remote Work
By Chatty Garrate. Follow her on Twitter. Remote-Workforce: A Trump Card or a Hindrance? Remote work has been around even before the world was hit by the pandemic. It has provided countless professionals—including those who belong to the IT sector a flexible alternative to earn money while concentrating on
Agile
The CatapultLabs team considers Retrospectives so valuable that not only do we run them frequently, we have also developed a tool that makes it really easy to perform them. You can say we are really into reviewing the past to realize how could things get better in the short term.
Agile
This post is from our Agile vault. Articles previously published on the SoftwareDevTools Blog that we're re-publishing. In that blog we discussed everything from Agile adoption, distributed work, and the Atlassian ecosystem. In the race to achieve agility, many software developer teams face obstacles during their daily work.