Planning an Agile project can be rather simple when all is known. When the market is predictable, requirements are clear, the technology is well understood, and the team is experienced in using all of the required tools, there isn’t much research required to complete a project. But for those times when all of the stars are not aligned and (God forbid) there is something the team does not fully understand, the team will need to dedicate some time to investigation or experimentation in order to complete the project. In terms of Agile and Extreme Programming (XP), this effort is known as a spike.
Software development teams new to Scrum often struggle with writing user stories. And the biggest challenge is usually incurred right from the beginning; defining the user role. While this can be challenging in any type of development, it is especially difficult in systems development. Read more
One value of Scrum that is often overlooked is visibility, which actually enables critical Scrum practices. Visibility is realized by communicating project status to all stakeholders, which includes the status of individual and team commitments, impediments, progress, along with other project metrics and indicators. Read more