Even after embracing Agile, some organizations still struggle to release software to customers as per their commitments. Here is an approach to help.
There's a challenge in blending the UX process with software processes. Here are few challenges that are commonly seen with UX in an Agile environment -- and ways we found to solve them.
Many factors play a part in the success or failure of any Agile initiative. We will present a series of articles to analyze the one factor that we deem most important: the intake of Agile projects.
Is your team facing difficulty in forecasting when projects will be completed? Are there large numbers of unestimated user stories in the product backlog? Does the planning meeting last several hours and is it full of confrontation?
One of the fundamental Agile values is, "We value responding to change over following a plan," which has sometimes been misinterpreted to mean that we don’t need to plan an Agile project. Nothing could be further from the truth.
Spring has sprung. Flowers are in bloom. Clocks have been adjusted to reflect Daylight Savings Time. All of these little indicators point to the undeniable fact that May the Fourth is just around the corner. . . .
I recently read an article about how Dhoni, captain of the Indian cricket team, deals with high-pressure situations in games. I've been thinking about how similar his thoughts are to the Agile Principles.
This is the true story of my team's beginnings with Scrum. . . .
Have you ever assessed the way your team follows Agile/Scrum? We have. Beforehand I thought we were working to a higher standard of Agile/Scrum. But I felt the opposite after seeing the assessment results. . . .
Even a standard user story is sometimes difficult to obtain from the stakeholder, because they have a vague idea about what they want. In such cases, the "Five W's" can be useful for writing user stories with complete and coherent information.
Your company (a start-up, small company, or a division of a larger company) has decided to build a new software product. You are in charge. What’s your first move?
Building a self-organizing team is one of the fundamentals of Agile software development, but there is no theoretical model for building a self-organizing team. I have built separate models of the progress of individual team members and of entire teams.
Testing rarely can be exhaustive, given that we have time constraints. How, then, do we ensure quality? One way is to focus on finding the highest-risk defects.
For me, Agile is a method that excels because it is value driven. Value driven means we're selecting (only) those requirements that are necessary and can give the best benefit in a competitive market.
Scrum has taken the industry by storm, and most IT organizations today are using some form of Agile/Scrum. But there are difficulties in implementing it effectively, and therefore in getting the benefits it offers when practiced correctly.
This article provides an overview of the situations faced in two of our teams' transition to Agile. We also cover the obstacles encountered, actions taken, and the phenomenal results achieved.
Without a shift-left test approach -- early and often -- developers and testers find it difficult or impossible to find defects until system parts are integrated in a system test. Why can't we reap the benefits of Agile?
There are situations where you find that it is not easy to create a cross-functional development team with a T-shaped skill set.
Chengliang You offers the first Scrum Alliance article in Chinese.
I have often heard teams say that Agile tools add no value. I would like to share some ideas, based on my practical experience, about how and why I think these tools do add value and can be more than just overhead.