The articles in this tutorial series were meant to provide you with a sound footing in software development practices, even if you are new to it and did not have prior experience. They were made simple and fun, and yet prepare you for success in managing and executing software development projects.
Below are a few resources for additional study and guidance. Many of them have further links to help you dig deeper. Read more
The demand for cheaper, faster and better applications will always be there, howsoever cheaper, faster and better you make them. This can be achieved only by making use of innovative applications, and not by reinventing the wheels.
But, as a business analyst, you are the best person to build the application (or most of it). This is logical because you understand the bigger picture, you communicate with the client, you visualize the app from day one with the client’s business objectives held dear to you, and you can communicate it best to the internal teams. So, you should be able to build all of the application or most of it…YOURSELF. Read more
Now that you have created a detailed document with features, it is advisable for you to create a traceability matrix (like the one shown here) in an Excel file matching each feature or functionality (in a column) to a requirement (in a row). This will ensure that all requirements are met.
This will also help you quickly identify which features are impacted when a change in a requirement is sought. Any time a change is effected in the requirements, refer to the matrix to identify the features impacted by the change and make appropriate modifications to the spec. Read more
According to surveys by the Standish Group, 20-25% of projects fail (or are challenged… never mind the terminology… just know that either the vendor and/or the customer is adversely impacted, and that is bad) due to poorly defined requirements.
Requirements must be absolutely clear and signed off by you and the customer. Read more
