CodeWeblog.com » coordination,software development,iteration » On the agility in the process of demand management

On the agility in the process of demand management


In fact, even if only the "logistics" This is a demand, I am afraid we can not be completed in six days inside. Therefore, I suggest that the marketing manager and then carefully sort out these needs and further the higher-ups know the psychological bottom line. "Logistics" are not afraid of difficulties in software development, but rather the coordination of SIM card, logistics, and other resources on customer service. Even before and logistics business has been an agreement, but it can not be generalized. Subsequently, the marketing manager and former co-operation through logistics providers have found that contact, just let the logistics to carry out the charges on behalf of, on the essentially impractical. Finally, "logistics" to by the wireless carrier's mobile service vehicles with cards, then by the students check their own cards. The most complex needs have thus been eliminated.

Although, I and the marketing manager who are not good, but I convinced him to come up with a project team iteration speed. As evidence that at 6 days, we still can not complete all remaining requirements. After further communication, finally we have identified two of the most urgent needs: "Online search and No.选号" and "boot-line." As long as these two requirements can be at 6 days of delivery, then this business can be successful at September 1 on line. Although the results may not be less attractive, but still completed a marketing manager and supervisor of psychological bottom line. All the remaining demand will be iterative as longer-term objectives, the project team just to give a more vague and awareness can be considered. Finally, we have these two requirements can be decomposed into the functions of measurement point, and once again removed a few trivial, it is difficult to achieve and deliver results on the functional significance is not much point. In addition, we also agreed that the acceptance test cases, and saved the form of language.

In the next six days, we have in accordance with the previous speed smoothly and successfully at September 1 to complete the iteration, the wireless operators are also ahead of other operators in the market opportunity in front of the occupation. Been encouraged by the project team.

In addition to the demand for access to quick, I would like to explain the demand for agile management. We at the Office of Internet business projects, use of lightweight project management tool Redmine as demand management tools. Although not a professional Redmine demand management instrument, but after our practice, and put it at agile demand-side management in particular on the right.

Redmine with "problem" as the basic unit of management, demand management in the agile sense, is a measurable "function point." Function Point has a sponsor, urgency, status, assigned to, the relevant question, start and end dates, expected working hours, tracking and description of property. Put demand through the decomposition of the functional point of record, we can demand of all the structural problem of management. As a result, developers face the past is not the kind of documentation of function point, but can be traced back, and easy to track as well as the structure of the Function Point. This software development organization and management has a decisive significance.

Redmine for the adoption of demand-side management, we also received a lot of extra benefits. One of the most important one is that the developers every day to participate in the function for the point that "time-consuming registration." These data provided the project team can quantify the speed of the iteration. The speed can be quantified after the demand for access and function points have a strong persuasive decomposition.

Through the above discussion shows that agile demand management project for the online business hall significance. Although the progress of the project is smooth, but the demand for the course, there are still some shortcomings worth considering. One of them is to demand acceptance of automated scripts to use. Project because of the complexity and particularity, automated inspection is still faced with numerous obstacles. This includes the Verification Code for picture identification, the correctness of the page language, unified billing local simulation environment and so on. Therefore, the online business hall project acceptance testing is still very much dependent on the artificial. Fortunately, wireless operators have a huge customer service system, making this problem will not stop the progress of the project. Another regret is that at Redmine Medium, unable to function at packing. In other words, it is not able to "user card" or "use cases" to organize the functional point. However Redmine is a open source tools, we will in future projects, combined with their own practice, and attempt to improve the fit to make them more agile demand-side management.
Digg Technorati StumbleUpon Mixx del.icio.us Reddit BlinkList Furl YahooMyWeb feedburner

Tags: coordination (RSS), software development (RSS), iteration (RSS), demand management (RSS), mobile service vehicles (RSS), measurement point (RSS), sim card (RSS), functional significance (RSS), accep (RSS), marketing manager (RSS), wireless carrier (RSS), term objectives (RSS), ups (RSS), six days (RSS), agility (RSS), logistics (RSS), bottom line (RSS), supervisor (RSS), customer service (RSS), cards (RSS)

Permalink: http://www.codeweblog.com/on-the-agility-in-the-process-of-demand-management/

Leave a reply