Scrum-based development “from scratch” projects that are based on a traditional monolithic architecture are prone to failures. The objective of this article is to understand the causes—and propose a possible solution based on microservices with a contract-first architectural approach.
Just because you are working in a waterfall organization doesn't mean you can't be Agile. Join Dave Prior as he walks you through a case study on implementing Scrum in a waterfall environment. He offers some key practices and data points that will enable you to be successful in both keeping the team productive and providing the information needed to build trust and confidence with the Project Sponsors and Senior Executives you need to support your Agile implementation.
Save Time With Tools And Templates
Product management is often a murky role: poorly understood and inconsistently practiced across tech companies – and often confused with program and project management. Yet done well, product management is a driver of market success and effective development.
This webinar is about making project management and innovation to co-exist through better understanding concepts around Kaizen and Kaikaku.
Learn From Others
Many companies are outsourcing to India, and the process of creating an agile, distributed team could have many potential pitfalls. Here, lessons learned are shared based on two years of continuous improvement to get a strong, contributing agile scrum team.
Within the scrum framework, the responsibilities and accountabilities of the scrum team as a whole align to the project management activities defined within the PMBOK® Guide. Understanding how these roles align helps to determine how a traditional project manager can transition into a scrum team on an agile project using the scrum framework.
Perhaps—like 500,000-plus other people—you have some form of Certified ScrumMaster® (CSM) credential and are looking to distinguish yourself and continue your learning journey. For credential seekers, this article explores some common paths.
While there are many governance data points that can be gathered and analyzed to help make go/no-go decisions, there are three in this writer's experience that stand out as being the most important.
The easiest solution is not always the best. It is more effective if you choose the best methodology for each single project based on its nature. Scrum doesn’t fit all projects’ needs. Kanban is another agile methodology that, believe it or not, works more smoothly for at least one type of project. But what type?
As more organizations become agile, clear, real-time communication becomes increasingly important. Here are a few tips to keep in mind to ensure your communication remains effective a new fast-paced environment.
What is the ideal tester-to-developer ratio for the development team? On the surface, this might sound like a perfectly reasonable question—one that should be easy for an experienced practitioner to answer. However, when you look deeper into the question, you will see that it has layers of underlying assumptions—including ones about corporate culture, politics and the likely skills of their own staff.
Agile practitioners generally agree that regular retrospectives throughout the project are a good practice; however, many are not seeing the full benefits from the practice. This article shares a number of tips on how to perform retrospectives effectively—getting the maximum value from this important agile process.
This real-world example looks at how agile principles were applied to an international company’s global ERP project. It discusses how agile was used to provide continuous feedback into how the project operates. It discusses many of the company’s lessons learned and how it solved challenges in a typical waterfall environment using agile principles.
Ask a Question