-
What is the Purpose of the Sprint Retrospective?
10 Ways to Improve Your Next Sprint Retrospective Meeting Previous Published on Propelo.AI What is the Sprint Retrospective in Scrum? Dictionary.com defines a retrospective as the “looking back on or dealing with past events or situations.“ It’s a reflection of sorts. And in the case of a sprint retrospective, it’s the reflection of past sprint events — a meeting between various members of the engineering team and stakeholders in the organization. Everyone has a chance to speak — and every voice is valued. So, what is the purpose of the sprint retrospective meeting? Who attends this meeting? And how often does it happen? Within the Agile framework, there are what you call the five…
You May Also Like
Voices.com empowers voiceover talent with insight on 2013’s voiceover industry
TelePacific Signs with Aligned Communications to better serviceTexas
Biotricity Invites Physicians to Join Shared Revenue Opportunity, Provides Clinics with Remote Devices for Improved Monitoring and Diagnosis
-
Startup Obtains Industry-Leading Certification, Continues Focus On The Future Of Engineering Excellence
Previously published to NewsBreak Last week, Propelo Inc, the world’s leading engineering excellence platform, dropped some pretty exciting news within the DevOps community. Known for its no-code workflow automation, the company recently attained its SOC-2 Type II certification, proving that it truly values data privacy and security. The credential was awarded to Propelo under the Trust Service Principles (TSP) and Criteria framework developed by the American Institute of Certified Public Accountants (AICPA). After undergoing an extensive certification process, the company remains committed to protecting its enterprise-level clientele, and their most crucial data, while excited to move forward as “the future of engineering excellence.” Propelo is “quickly becoming a vital management tool” in the eyes of…
-
What Are Engineering Analytics?
Previously published to Propelo.AI on the future of data and engineering excellence Data is propelling new business. And its impact on the business community has, in a way, become an art form. And the art of understanding business data, or business intelligence (BI), is centered on a company’s ability to read, transform, optimize and present this data between both technical and non-technical teams. As a result, it empowers businesses to improve operations, optimize internal processes and evolve their workforce in ways they have never done before. Engineering teams can make that happen. In fact, they are in a better position to drive data within the enterprise space than most other departments. They…
-
What Is Technical Debt? A Complete Overview
Previously published the reasons why some take on debt — intentional or unintentional — on Propelo.AI Small risks can sometimes equal big gains, and many consider technical debt a risk that they are willing to embrace in order to get ahead. But what is technical debt, and how risky can it truly be? At its core, technical debt is a tradeoff that engineering organizations make in order to deliver software on time, or to stay ahead of the competition. It’s essentially a set of activities, foregone due to time constraints of release schedules and prioritization. These activities could range from features that are frequently dropped from release to release, because they don’t…
-
Agile Velocity – Good Metric, Use With Caution
The Do’s and Don’ts of Using Velocity in Agile | Previously published to Propelo.AI Agile velocity is a very simple concept that software development teams use to gauge how many tasks can be performed, or completed, on average within a given timeframe. Unfortunately, while it can be extremely useful within the field of project management, it can also be very detrimental if used incorrectly. According to Youtuber Gary Tsang, Your Agile Coach, “Agile velocity is one of the most popular software development metrics in the world. When used for an agile team’s sprint capacity planning, it can be extremely powerful. But some people, some organizations and some teams use it for…
