Business Analysis Articles

Oct 27, 2024
1751 Views
0 Comments
Fear is a powerful motivator. It often drives us to hold onto the familiar, resisting change, even when the change might bring progress. This fear—of the unknown, of disruption—feeds into status quo bias, a cognitive bias that compels individuals and organizations to stick with establish...
Fear is a powerful motivator. It often drives us to hold onto the familiar, resisting change, even when the change might bring progress. This fear—of the unknown, of disrupti...
Psychological safety has been reported to result in increased knowledge sharing among software development team members. Studies found a positive correlation between social interac...
In the vast landscape of project management, few challenges loom as large and insidious as scope creep. It's the silent saboteur that can derail even the most meticulously plan...

Latest Articles

24475 Views
17 Likes
1 Comments

As the process of capturing and documenting business requirements matures, there is often a watershed moment when an organization must decide whether to perform traceability of requirements as part of that process. Most companies involved with a formal methodology for software development utilize some degree of traceability; but those not familiar with it could be put off by the overhead of requirements management (RM), of which traceability is a component. Therefore, it helps to understand some of the value aspects of instituting traceability.

12684 Views
9 Likes
0 Comments

Anyone perusing the computing rags (or their online equivalents) will no doubt have noticed that this year's big thing for applications development is a combination of Cloud Computing and Software as a Service (SaaS). I'll talk about Clouds in a future blog, as I want to concentrate on the SaaS phenomenon today.

19271 Views
4 Likes
1 Comments

Businesses cope with manual, repetitive tasks to get the job done. Email, conference calls, and "walking the cubes" are too frequently the process for requesting information, getting approvals, and checking project status. Time and resources are wasted, errors abound, and everyone is less productive.

Automating these everyday business processes is the way to improve productivity and gain efficiency. Traditional Business Process Management (BPM) systems can provide a solution, but the cost and complexity to implement simple processes is often too expensive for many business units.
 

20712 Views
11 Likes
0 Comments

For almost every analyst, the day comes when you write a set of requirements that causes engineers to bemoan a recent development project that they just coded. "If only we'd known that you wanted to build this, we would have made the last project more flexible. Now we've hardcoded in changes that will take days to rebuild."

27502 Views
15 Likes
3 Comments

The title of "Business Analyst" is one of the fastest growing in the IT industry. In fact, the United States Department of Labor projected a 29% increase in computer systems analyst employment by 2016. There are many resources available that explain what a business analyst is, often in terms of comparing the responsibilities of an analyst to those of other team members we're more familiar with, like project managers, software testers, and systems architects.

14693 Views
17 Likes
1 Comments

A long time ago, before Business Analysts existed, it was believed that people in the business would be able to define their own requirements.  When a business department wanted to have a new piece of software, they would go to the IT department and the developers would ask them what they wanted. The business people would express this as best they could by writing down lists of things and having meetings to explain them, and then the IT department would build or buy whatever they seemed to want.
 

28729 Views
17 Likes
1 Comments

Systems work is not as hard as you might think. However, we have a tendency in this business to complicate things by changing the vocabulary of systems work and introducing convoluted concepts and techniques, all of which makes it difficult to produce systems in a consistent manner. Consequently, there is a tendency to reinvent the wheel with each systems development project. I believe I owe it to my predecessors and the industry overall to describe basic systems theory, so that people can find the common ground needed to communicate and work. Fortunately, there are only four easy, yet important, concepts to grasp which I will try to define as succinctly as possible.

9718 Views
5 Likes
1 Comments

The business analyst's job has changed this year -- and so have the critical skills that companies demand. New research shows that while communication is still key, knowledge of Lean and Agile methods is a must-have as well.

42923 Views
20 Likes
8 Comments

In Part 1 of  this article, I talked about the new skills and attitudes business analysts need to bring to agile development... Now it's time to talk specifics. What exactly do BAs do in agile development? How will your activities differ from those of traditional development? Let's take a look at agile business analysis from the perspective of the activities that make up requirements development and management, comparing traditional with agile analysis.
 

17235 Views
8 Likes
1 Comments

Although it may seem obvious that the User Interface (UI) directly impacts usability, and therefore satisfaction, Business Analysts often find themselves focusing on functional requirements to ensure end user satisfaction. Mainly, this is due to the non-functional requirements, like usability, being dictated by existing technology or process within the organization. However, research into mobile user interfaces is placing the focus back on the usability requirements as the main driver of user satisfaction.

Page 67 of 67First   Previous   58  59  60  61  62  63  64  65  66  [67]  Next   Last   

 



 




Copyright 2006-2024 by Modern Analyst Media LLC