Agile Methods

32451 Views
46 Likes
0 Comments
Sequential Development is the traditional approach that allows the business analyst to perform business analysis during the initial phases of a business process. The novelty brought by Agile was that it challenged practitioners to perform business analysis throughout the entire development process. This is a fundamental difference between Agile and Sequential Development because Agile recommends the continual re-evaluation of the initial business analysis. The present article will discuss business analysis in Agile by focusing on Scrum implementation.
11880 Views
51 Likes
0 Comments
The Agile Manifesto was born out of frustration by a group of developers who were fed up with how software was being developed. Software development is a learning experience and no one understands this better than those who are actually writing the code. Waterfall was a misguided concept that seems reasonable on the surface but does not work in reality. Since software development is a learning process it is impossible to think of every single requirement up front and have them signed in blood before starting development.
49226 Views
44 Likes
4 Comments
This article extends design thinking into a process and method that uses a range of common Business Analysis techniques to drive engagement through collaboration. It provides more structure to either side of the creative process to one better frame the domain of concern, and secondly after creativity has produced ideas, to prototype, refine, test and learn. The article also positions this process as a better way to arrive at a business case or pre-project phase, since it provides enormous insights through an engaging discovery process; something that would never occur within a traditional environment into investigation investment feasibility.
25011 Views
8 Likes
0 Comments
Agile, formally introduced in 2001 through the Agile Manifesto, has morphed into many variations and been customized within organizational cultures and projects. After 14 years since its introduction, this article raises an important question.
26014 Views
9 Likes
0 Comments
A product roadmap is a powerful tool to describe how a product is likely to grow, to align the stakeholders, and to acquire a budget for the product. But creating an effective roadmap is not easy particularly in an agile context where changes occur frequently and unexpectedly. This post helps you create an effective agile product roadmap using my roadmap format, the GO product roadmap.
28477 Views
23 Likes
1 Comments
If you are a Scrum Master of an agile team, your prime purpose is to help the software development team remove obstacles that are impeding progress. The best practice approach in succeeding at this is to assume the role of a neutral facilitator. That is, the Scrum Master guides the team through a process for solving situations themselves rather than the Scrum Master proposing a solution. This article provides two workshop scenario exercises (an internal team conflict and a team conflict with the product owner) that help the Scrum Master practice the neutral facilitator role.
28078 Views
24 Likes
1 Comments
During a recent project where we were adopting aspects of Agile into a very waterfall environment I found myself repeatedly verbalising the concept of ‘definition of done’ to project owners and sponsors. This explanation was met with satisfied faces from people who loved the concept. This lead me to think how this seemed to be a revolutionary concept where it is something that I live by and strive to do everyday.
19762 Views
3 Likes
0 Comments
Creating a product with a great user experience requires more than just user stories. While capturing the product functionality is important, the user journeys, the visual design, and the nonfunctional properties have to be described too. Stories should be complemented with other techniques including scenarios, storyboards, and design sketches.
74692 Views
44 Likes
0 Comments
The 3 Amigos (sometimes referred to as a “Specification Workshop”) is a meeting where the Business Analyst presents requirements and test scenarios (collectively called a “feature”) for review by a member of the development team and a member of the quality assurance team.
47092 Views
5 Likes
0 Comments
User stories are probably the most popular agile technique to capture product functionality: Working with user stories is easy. But writing good stories can be hard. The following ten tips help you create good stories.
22889 Views
30 Likes
19 Comments
In the past few years, software development has been shifting more and more from traditional to agile practices. This change impacts how business analysts perform their role. Here are three key aspects of the business analysis work that are different in an agile environment
34048 Views
25 Likes
4 Comments

Tracking project status means comparing where you really are at a particular time against the expectation of what “complete” means for this development cycle.  Monitor the status of just those functional requirements that were committed for the current release, because that’s the set that’s supposed to be 100 percent done before you declare success and ship the release.

24433 Views
21 Likes
1 Comments

Do “Agile”projects need written requirements? Let us answer this question in this short article. As you may know, more and more software development teams have been adopting “Agile”processes over the past decade or so. As you may also know, Agile development processes such as Scrum and XP emphasize “working software” over requirements documentation.  Does this mean detailed, written requirements should be avoided in Agile projects?

19514 Views
14 Likes
0 Comments

While the benefits of an effective Business Process Management solution are clear, a truly successful, on-time implementation can prove elusive. As a Business Analyst, you may be held responsible for project timelines. So when the schedule starts slipping, your credibility can slip away with it. This article discusses how agile technology and processes can slash implementation times from months or years to a few weeks or evendays, reducing time to value and ensuring successful, on-time, on-budget implementations.

15412 Views
10 Likes
1 Comments

In an ideal world, a single, full-time, expert user would indeed be sitting within view—“on sight”—of developers, ready at a moment’s notice to speak definitively for the entire user community. In reality, this is unlikely in most situations.

Page 5 of 10First   Previous   1  2  3  4  [5]  6  7  8  9  10  Next   Last   

 



Upcoming Live Webinars

 




Copyright 2006-2024 by Modern Analyst Media LLC