|
Writing in an Agile World Sarah Johnson explains the role of writing in an agile world and how to educate your team members. Remember, agile takes into account that each situation is unique, and you need to determine what makes the most sense for your particular Scrum team.
|
|
|
Using Agile for Requirements Management Charuta Phansalkar writes on the necessity of capturing and understanding requirements using agile practices. Agile, when implemented effectively, will ensure that the customer's voice is clearly understood throughout the project, which results in maximum customer satisfaction.
|
|
|
Internationalization Best Practices for Agile Teams Marcia Rose Sweezey and Stefan Visuri explain two best practices that are defined for agile teams in their organization. Read on to discover how externalizing strings and conducting pseudo-language testing during each iteration and sprint will give you the most payback for the least investment.
|
|
|
Product Backlog Hygiene: Prepare to Be Groomed How do you start with a product backlog when you’re transitioning to agile? In this article, Darin Kalashian shows us how a cross-functional team at the product owner level creates a product backlog.
|
|
|
Can a ScrumMaster Be an Effective Leader When Working Remotely? Mariya Breyter explores the role of a ScrumMaster and whether or not one can work effectively when working remotely. If the ScrumMaster is not available to orchestrate product delivery, bridge any gaps, and remove any obstacles, a product will never be delivered—even worse, a wrong product will be delivered. In order to achieve this understanding, the ScrumMaster must show value to the team as a natural leader, no matter if he is onsite or remote.
|
|
|
Programming with an Agile Mindset 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.
|
|
|
Top Twelve Myths of Agile Development 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.
|
|
|
Management Myth 13: I Must Never Admit My Mistakes 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.
|
|
|
Essential Methods for Agile Project Success 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.
|
|
|
End and Then Begin Again 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.
|
|