LinkedInFeeds

Translate Requirements is Vital

By

Comments

Post a Comment

Popular posts from this blog

Wireframe a Prime part in Design

By
Image
Wire frame using pencil drawings                                                                                                Why Wireframe is Important? The timely feedback from the project stakeholders is most important. The early feedback from stakeholders will boost the satisfactory solutions to the problem identified or goal in a project. Never expect anyone to read through hundreds of pages of text only specifications. Instead, the better is to provide any visual representation to which they can refer and react or post any suggestions or comments for better solution which will be delighted and expected for the goal achievement. Wireframes provide an excellent solution to this problem in a web based platform / window based in a desig...
Read more

The Toyota Way – Types of Wastes – IT industry

By
Image
  The very first piece, I wish to clear the misconception that, the Lean management is applicable for Manufacturing. No beloved readers! It is not true; the Lean management can be applied in any industry even in the personal events. Let’s see the type of mistakes that are mostly applied, experienced in the IT industry, referring to Lean Management genre. 1) Overproduction This can be termed effectively as faster than the necessary pace. Specifically, in the Business analysis, the faster inferring the solution without validating the assumptions, specifications will havoc and down run the entire project life cycle. Overproduction (Faster than the necessary pace) is observed in all the project life cycle. 2) Waiting The Business analysis activities are completed, and development were not started due to various reasons. I would say this as proper fitment of pipeline. If there is spills in the pipeline in movement of activities, the efforts are required to re-order/ re-align. It should...
Read more

Writing Requirements - Consider Some Points For Success

By
Be specific In Requirements      When stakeholders are be very clear in their need, Business Analyst should not consider that it is final requirement and write it down on paper. There is still more specific in requirements. Ask more questions to business users to make requirements more specific. The other trap is you should identify the correct user to question on requirements. To be more specific, i have stated a below example for better understanding Need identified is : I need a invoice report every month. Other Questions to be asked to stakeholders are : Why you need, When you need, How you need, Which time you need, In which format you need and still more. Drill down to become the requirements more specific. Bring Your Testers Early In project     Every requirement should be testable, reliable. For each requirement translate in to a test case. Quality is very important in meeting the Business need. Success Factors Of A Project ...
Read more