This is the last post in the Getting Requirements Right series. Here I am going to discuss requirements, their types and examples.
This is part 4 of the Getting Requirements Right post series, and in this post we’re going to explore Use Cases and how to better use them.
In the previous post, you learned about Agile approach, Epics and Themes. Today, in part 3, we are going to dive into User Stories, another useful Agile technique.
This is part 2 of a 5 part series of posts where I talk about getting requirements right and delivering them faster. In this post, I’m going to discuss process design.
In this series of five posts, I’d like to talk about getting requirements right and delivering them faster. My goal is to provide you with new techniques and approaches for producing high quality requirements on your projects.
Cybersecurity has become a familiar theme in the news. It impacts businesses, ranging from start-ups to global companies, all around the world.
We live in the era of constant change, as we hear daily in technology news and business meetings. Businesses are trying to keep up with the pace of changes by improving and transforming themselves. More and more initiatives and projects have to be completed “yesterday” meaning that they have very tight deadlines and high urgency.
While working on multiple projects over the last year, I noticed that they had similarities (evolutionary improvements were required) and as a result I applied similar sets of requirements to the solutions. In other words, patterns emerged.
You have probably seen the scary statistics of failed projects. They often reveal that the major cause of project failures is poorly defined requirements.
I’ve recently been involved in a discussion on how to better prioritise requirements. It’s an important topic because the requirements prioritisation process can get rather lengthy,and it’s good to speed it up.
The majority of business analysts don’t have the tools which would help them work more effectively. We’ve identified some problems which we can solve by developing a requirements management tool. You could help us make it more useful to you by providing input and feedback.
A large portion of IT projects fail or are challenged in some way. The cost of failed IT projects can be enormous. This article examines the impact of requirement quality on the project and business as a whole.