Use MRD To Control Outsourcing

Is your software development process to predict the number of weather? Is your software shadowing caused six weeks of programming? Are you marketing requirements document (MRD) or magic to predict your software release schedule? At the beginning of my career, I worked in the lab for a company that sells microwave devices. I was responsible for the computer systems running HP software is used to design the circuit. One day someone from HP technical support comes through. He asked what we were doing in the lab. 

When I told him "microwave circuit design", he said, "Oh, I hear they use a lot of FM". I paused and tried to remember if the modulation frequency is actually used in the circuit. Before I could answer, the man from HP continued, "Yes, it takes a lot of F ----- g Magic to make the circuit work!" He's right. The main issues in microwave circuits in their day by creating high-yield manufacturing process. Too often have a lot of tuning and adjusting individual devices with a toothpick and tweezers to make shipment dates.Since then I have worked on several software projects where some amount of "FM" released.

How needed to get the software on the device projects your software? Do not drift along never seem to finish? Do they require heroic efforts of a few individuals to carry out the delivery date Outsourcing can solve the problem of delayed release software with more force than your software development process -? More process than is typically used in an organization where every person working nearby. Outsourcing vendor should have clear processes and efficient communication to be successful. Software development is all they do. Outsourcing not only give you the benefits of having software that is made for less cost, but also a process that provides increased predictability, results and success.But many still fear outsourcing. The number one concern is the loss of control of client software development process.One revealed in this way. "I can not just tell the programmer what to do every day. 

It would be like hiring a contractor to build a house and asked him to put a window in the door there and here. You have to understand what effect that will have on plumbing and electrical and building a rest house. "He's right. You must have some idea about the architectural and construction plans. Working with multiple programmers in the same room can let you take shortcuts and informal sharing plan through word of mouth. "Just put a pop-up window here." Except for small projects and simple, informal communication does not work. Need a description of the requirements for the software. You need to find a way to communicate efficiently with your software needs so that you can move beyond the stage "idea" with a vision for your software.The first step in creating a software product to write a Marketing Requirements Document or MRD. It contains a brief description of all the features, functions and benefits of the product you must have to be successful in the company marketplace.Some make the difference between MRD and PRD - the product of Document requirements. PRD has more details about the software what to do. 

For example, you need both an MRD and PRD when you create a variety of services and products. MRD describes the product strategy, market positioning and sales channels needed to deliver product with a particular set of functions in the market. PRD on the other hand focuses on the detailed requirements of the software itself.The MRD or PRD should include the basic architecture and the user interface is important for your software: * Software architecture * Hardware Platform Selection * User interface functional specifications * design * Multiple "use cases" ; that describes how users interact with your software * Story demo board (optional) * Major milestone release schedule * Quality Assurance testing requirements * Technical Documentation * Detailed schedule (until the completion of the first major milestone) * Cost estimate of cost-effective and time-effective developmentYour outsourcing marketing or MRD requirements document describes the functions of the software product and how it can be sold and distributed. It is also a device to control your software development process, especially if you are outsourcing. If you are running the risk of delays, poor quality and not just knowing what you are doing.

No comments: