Agile is recognized as a system-software development approach used to get quick feedback to keep the customer involved at every stage, build a disciplined team, and have working software at any given point in time. Sameer Arora writes on how things can fall out of place when agility on the programming side is ignored.
When it comes to agile development, Allan Kelly has noticed a lot of misinformation is being passed off as fact. In this article, Allan takes a closer look at twelve of the most common agile myths he has encountered while training new agile teams.
Managers are people, too. They have bad-manager days. And, even on good-manager days, they can show doubt, weakness, and uncertainty. They can be vulnerable. Managers are not omnipotent. That’s why it’s critical for a manager to admit a mistake immediately.
Mark Balbes presents a framework for agile project management’s critical techniques. These techniques are required for successful agile development, where rapid requirements changes can be followed through with rapid development changes.
Shweta Darbha explains how teams can review their work and improve themselves after the completion of key projects or after they have adopted Scrum. Learn how your own team could benefit by following this practice after your next project.
A Scrum Master has only allegiance to the team. A project manager has responsibility to the team and to the organization. That means that the project manager might feel torn when the organization pressures the project manager to do something stupid.
It can be tricky for managers and technical leaders to make the transition to agile. They’re likely accustomed to doing things a particular way. What’s more, they may try to squeeze their old ways into the new, agile approach. Here, Johanna Rothman describes why that isn’t a good idea, especially regarding stories that are too big.
Charles Suscheck compares the levels of productivity of Scrum and Kanban through a hands-on experiment that he and his team personally participated in. Learn the upsides and warnings about each practice to help you decide what might work best for you and your team on your next project.