As companies transition to Agile and Scrum to manage their software development projects, how does this affect the work of business analysts?
234 items found
This year's top 10 business analysis trends focus on leveraging the power of requirements at all levels through Agile and business architecture to deliver business value to the organization.
The role of a Development Manager can be a very stressful one. You are being pulled in different directions. If you are doing your job well, nobody notices. If things go wrong, no matter what the cause, it's your fault.
One expert used to think that ScrumMasters were not--and should not be--functional managers. But after coaching many teams, he's not so sure anymore.
You just got out of your CSM class, overflowing with your newfound Scrum knowledge and renewed faith in software development practices. You're ecstatic to share your new view of the world and show how Agile can benefit your organization, and you can't wait to get started. But, in your first Agile project, you meet resistance, opposition, and worst of all, modified Scrum practices. What's a ScrumMaster to do?
Scrum is one of the most heavily used agile techniques. It's not about coding; instead, it focuses on organization and project management. Here's how one manager and team adopted Scrum techniques.
How long has Scrum been gaining popularity? How can a company benefit from doing Scrum? Those are just a few of the questions answered in this handy reference.
Here are 10 key benefits you will derive from following an agile approach to development.
Business value keeps getting diluted when software projects move from business executives to the IT folks. The plan that underpinned the business case of the investment is unfortunately often washed out when translating into IT and features in a software. This is a critical error and it is not easy to correct if starting development without it. Here are three models that can be used in combination, each serving it own purpose in the planning process.
"Scrum is easy; implementation is hard." You've probably already heard that many times. The same goes for some particular tools, like planning poker. The practice itself is very straightforward, but how to use it productively over a long period of time is harder. In this article, the author shares a simple, lightweight technique that makes the sizing process a little easier in the daily life of a Scrum team.