The Daily Standup (DSU) is a key ceremony in the Scrum Framework. When run effectively, it can ensure the Scrum team focuses on what’s important to meet the Sprint goal and commitment. When DSUs serve only as a status meeting, the value of the ceremony is lost.
Companies unleash their true potential in today’s ever-changing, constantly evolving world through digital transformation. Implementation of cloud-based Software as a Service (SaaS), when combined with Agile methodology and DevOps, represents a strong value proposition
There are a lot of advantages to behavior-driven development, but there are also a lot of challenges you can encounter during the implementation. Knowing is half the battle, so be aware of these eleven common stumbling blocks to BDD adoption and outline plans to mitigate them beforehand, and you’ll be able to start reaping the benefits of BDD sooner.
If you want to trigger long-running, end-to-end automated tests, you must integrate the test execution system with the continuous integration system. But this job falls in a fuzzy area that meets at the nexus of feature development, test automation development, quality assurance, and build and release engineering. Here's how to decide who should be responsible for the setup.
Suppose we’re looking at a system rewrite where the stakeholders have none of the original engineering documentation. (This isn't surprising; documentation becomes obsolete—or even misleading—as the system changes, and corresponding docs don't get updated.) What can we do? Here are some tactics to use—and risks to anticipate—when testing a system rewrite.
When a company makes the move from software as a service (SaaS) to an API-first platform, a change in mindset is required. The successful transitions come from those who shift from features to flexibility. Technology teams should look to remove constraints and broaden the possibilities of their platform by constantly exploring ways to make their platform as flexible as possible.
Continuously improving your configuration management practice results in delivering high-quality, complex software beautifully and efficiently. But it’s equally as important to observe the entire CM process so you can envision and plan for worst-case scenarios as well as think about how you can scale with time—and keep on improving.
Software development is an elaborate process, so many organizations follow defined procedures. But it can be difficult to keep track of every step. It is often helpful to try to visualize the complex processes involved; seeing them outlined can help you understand what needs to be completed and how to manage the overall effort.
Application lifecycle management shouldn’t enforce existing IT and software delivery environments; the idea is to integrate as many tools and processes as possible into a unified workflow. The ALM journey continues forward, and, as technical and process trends come and go, the core principles are perhaps more relevant than ever.
Status accounting is following the evolution of a configuration item through its lifecycle. Using application lifecycle management along with agile helps prevent mistakes, but lets you have the minimum amount of red tape; the team achieves an acceptable velocity without being unduly burdened with too much process.