Some processes, problems, and projects appear complicated, yet their complexity disappears as soon as one takes a closer look and breaks them down into simpler parts. This is the objective of functional decomposition - to clarify how the overall functionality emerges from the interaction between individual components in increasing detail.Read More
The key importance of problem tracking is seldom evident when there are just two or three problems to overcome at the same time; it doesn’t take much to stay organized in such situations. It gets much more complicated, however, when the number of problems increases, especially in the early phases of software development projects.Read More
In a perfect world, our plans would always go according to our expectations, and nobody would ever make a wrong decision. Sadly, we don’t live in a perfect world, and things don’t always go according to plan. Knowing that mistakes are inevitable, the question is how to improve our practice or reduce those mistakes the next time we get an opportunity.Read More
There are some major tell-tale signs to look out for when improving processes. These trouble spots exist to varying extents in most poorly-performing business processes. The objective of any improvement effort is therefore to minimize these as much as possible to ensure that affected processes perform as efficiently as possible and deliver value to the business.Read More
The most obvious benefit of gathering stakeholders with different backgrounds in a single room is the increased chance of spotting defects in requirements before development or implementation begins. Structured walkthrough sessions also raise awareness about the different development or maintenance methodologies.Read More
State diagrams typically describe the states of an object, the transitions between the different states and the events that trigger those transitions. Thinking through objects in a system and their respective states can also help to identify missing requirements.Read More
A problem statement defines the problem being faced by a business and also identifies what the solution would look like.
It can be seen as the starting point for coming up with a product vision. In defining the problem statement, be sure to include these elements:Read More
Six Sigma has continued evolving over the years, and focuses on improving customer satisfaction, meeting stakeholders' requirements, and improving the outputs (products/services) offered by organizations.Read More
This technique is also known as “Item tracking” or “Issue Tracking" and it covers the supervision of defects, assumptions, actions and issues until they are resolved. It provides an opportunity for stakeholders to rank the importance of issues affecting them.Read More
In developing a business case or a feasibility study, many activities are associated with inherent uncertainties and therefore, estimating the resources required to complete such project activities can be a challenging task for the business analyst.
Great project estimation commonly involves applying one or more techniques in arriving at time and cost estimations, some of which are discussed in this article.Read More
Business analysts can use VRIO to accurately assess the internal resources of a business, its competitive advantage potential, and possibilities of improvement of relevant resources within affected business areas.Read More