Considering the reasons for systems projects, is it possible to have too much of
ID: 3606873 • Letter: C
Question
Considering the reasons for systems projects, is it possible to have too much of a good thing? Can service ever be too good? Can performance be too strong? Can there ever be too much information? Can controls be too strong? Can costs be reduced too much? Why or why not? If so, where should a line be drawn? Considering the reasons for systems projects, is it possible to have too much of a good thing? Can service ever be too good? Can performance be too strong? Can there ever be too much information? Can controls be too strong? Can costs be reduced too much? Why or why not? If so, where should a line be drawn?Explanation / Answer
Considering the reasons for systems projects, is it possible to have too much of a good thing? Can service ever be too good? Can performance be too strong? Can there ever be too much information? Can controls be too strong? Can costs be reduced too much? Why or why not? If so, where a line should be drawn
Every project having its own goals, timing, deliverables and cost effictive journey. In order to collaborate all the things in same phase, we need to have a detailed project planning. According to the project planning, project scope will be reamins.
Every system project should be basic requirements from stackholder as follows..,
Canservice ever to be toogood: => Its manditory
As project concern , service need to be up to the mark, otherwise impact on the revenue of overall product in end user pointview. So service to be required to attract the customer and maintain the 24*7 service which is essential these days
Can Performance to be good: => Performance leadsto the project existence
Performance of project is makes vital role in overall product journey. While considering the project performance, we need to take care how far particular project remains in current world. Everytime need to check which tool using, durability and performance of specific tool.
Can there ever be too much information : => Ist most important aspect
For any project planing maintaining the documentation and information sharing is very important.While development, knowledge sharing is very import which is documented and transparent between all developers. If not project goes into wrong direction. Even though production phase, if know people not exists in organisation, in order to resolve the issues, we need to depend on information. So this is essential thing.
Can controls be too strong: depends
I’m not complete agree on this. Depending on the flexibility and ideas from developers we can introduce new essentials and tools. According to the latest world, durable project need to having less control.
Can costs be reduced too much : tentative
Cost effictive is import but it’s not strict to strict figure. It will ruine the project scope. Based on the fund provided to the project, project path will be defined. So need to be having standard people in the project, if we do cost cutting on this overall project will be impact. So overall Cost to be well defined and flexible.