Business Analysis (BA) is a growing profession which is helping organisations to manage business transformation in an ever changing and complex world. Business analysts work across the business change lifecycle; they develop early understanding of business needs so that the right projects are funded for the right reasons and ensure that the solutions are developed that meet these needs. As a result, the Agile philosophy and techniques are fundamental to business analyst’s work.
When you start scaling Agile, you might need more metrics to assess you software development process. In this article, Janani Rasanjali Liyanage proposes some metrics that adhere to Lean and Agile principles to measure business agility in terms of predictability, reliability and adaptability.
Managing the product backlog and prioritizing the user stories if one of the main responsibilities of the product owners in Scrum. In this blog post, Andy Carmichael explains how to assess the priority of product backlog items using the cost of delay.
Non-functional requirements relate to qualities of the system that cut across user facing features, such as security, reliability, and performance. How does an Agile team take care of these non-functional requirements? This presentation discusses if user stories are of any use in this situation and how Scrum teams can applying Agile techniques to solve these concerns.
This article examines the Agile myth that constant process improvement is imperative. It discusses the fact that if you need to continuously observe your process, you should wait for the pauses between iteration to perform process improvement.
This talk provides a is a reflection on what Michael De La Maza has learned as an Agile Coach about communication, emotional stress and team organization.