Critical Path Analysis
The red line in the diagram denotes the critical path. It can be concluded after analysing the critical path that the project will take 60 days to complete. Considering the slack time of the project plan, it can be observed that there are some activities which can be delayed little further and it will not delay the project. For example, in case of testing, the unit testing can be delayed until 29 days. The integration testing can be delayed till 67 days. Likewise, the summary activities- documentation, deployment and pilot all have the slack time, and they can be delayed to a certain extent.
The project manager has prepared the project plan for the CRM software development. The project will take 107 days to complete. However, the duration of the project can be shortened by executing some project activities in parallel. In case of testing, the tester can carry out the unit testing and the integration testing in parallel; it will save a lot of time. The documentation of the software project can be prepared right after the testing. Therefore, the technical communicators can work on the documentation while the trainer is busy training the end users. Again, the pilot and the deployment project activities can be executed in parallel. In this way, the project manager can optimise the duration of the project by choosing the predecessor wisely.
The table showcases a list of activities along with the resources. The resources have been distributed among the activities uniformly. The project is not overloaded with resources and is not running out of the schedule. The project will take 107 days. The stakeholders will have to complete the project within the fixed deadline that is 107 days.
Management, project manager, developer, technical communicators, deployment team, analyst, testers and trainers have been allocated for the project. The standard rate has been scheduled for the resources as well. Since the project is not overloaded with resources and is not running out of schedule, no changes will be made in the resource sheet and in the project plan.
The project budget has been scheduled to $649, 200. Since the project is not over-allocated and is not running out of schedule, therefore no changes have been made in the project. The project budget remains the same. The overall budget of the project is shown below in the table-
|
Task Name |
Fixed Cost |
Total Cost |
Baseline |
Variance |
Actual |
Remaining |
|
CRM Software Development |
$0.00 |
$649,200.00 |
$0.00 |
$649,200.00 |
$0.00 |
$649,200.00 |
|
Scope |
$0.00 |
$24,800.00 |
$0.00 |
$24,800.00 |
$0.00 |
$24,800.00 |
|
Determine project scope |
$0.00 |
$4,000.00 |
$0.00 |
$4,000.00 |
$0.00 |
$4,000.00 |
|
Secure project sponsorship |
$0.00 |
$8,000.00 |
$0.00 |
$8,000.00 |
$0.00 |
$8,000.00 |
|
Define preliminary resources |
$0.00 |
$6,400.00 |
$0.00 |
$6,400.00 |
$0.00 |
$6,400.00 |
|
Secure core resources |
$0.00 |
$6,400.00 |
$0.00 |
$6,400.00 |
$0.00 |
$6,400.00 |
|
Scope complete |
$0.00 |
$0.00 |
$0.00 |
$0.00 |
$0.00 |
$0.00 |
|
Analysis/Software Requirements |
$0.00 |
$74,000.00 |
$0.00 |
$74,000.00 |
$0.00 |
$74,000.00 |
|
Conduct needs analysis |
$0.00 |
$20,000.00 |
$0.00 |
$20,000.00 |
$0.00 |
$20,000.00 |
|
Draft preliminary software specifications |
$0.00 |
$12,000.00 |
$0.00 |
$12,000.00 |
$0.00 |
$12,000.00 |
|
Develop preliminary budget |
$0.00 |
$12,800.00 |
$0.00 |
$12,800.00 |
$0.00 |
$12,800.00 |
|
Review software specifications/budget with team |
$0.00 |
$5,200.00 |
$0.00 |
$5,200.00 |
$0.00 |
$5,200.00 |
|
Incorporate feedback on software specifications |
$0.00 |
$4,000.00 |
$0.00 |
$4,000.00 |
$0.00 |
$4,000.00 |
|
Develop delivery timeline |
$0.00 |
$6,400.00 |
$0.00 |
$6,400.00 |
$0.00 |
$6,400.00 |
|
Obtain approvals to proceed (concept, timeline, budget) |
$0.00 |
$7,200.00 |
$0.00 |
$7,200.00 |
$0.00 |
$7,200.00 |
|
Secure required resources |
$0.00 |
$6,400.00 |
$0.00 |
$6,400.00 |
$0.00 |
$6,400.00 |
|
Analysis complete |
$0.00 |
$0.00 |
$0.00 |
$0.00 |
$0.00 |
$0.00 |
|
Design |
$0.00 |
$75,200.00 |
$0.00 |
$75,200.00 |
$0.00 |
$75,200.00 |
|
Review preliminary software specifications |
$0.00 |
$8,000.00 |
$0.00 |
$8,000.00 |
$0.00 |
$8,000.00 |
|
Develop functional specifications |
$0.00 |
$20,000.00 |
$0.00 |
$20,000.00 |
$0.00 |
$20,000.00 |
|
Develop prototype based on functional specifications |
$0.00 |
$16,000.00 |
$0.00 |
$16,000.00 |
$0.00 |
$16,000.00 |
|
Review functional specifications |
$0.00 |
$16,000.00 |
$0.00 |
$16,000.00 |
$0.00 |
$16,000.00 |
|
Incorporate feedback into functional specifications |
$0.00 |
$8,000.00 |
$0.00 |
$8,000.00 |
$0.00 |
$8,000.00 |
|
Obtain approval to proceed |
$0.00 |
$7,200.00 |
$0.00 |
$7,200.00 |
$0.00 |
$7,200.00 |
|
Design complete |
$0.00 |
$0.00 |
$0.00 |
$0.00 |
$0.00 |
$0.00 |
|
Development |
$0.00 |
$105,600.00 |
$0.00 |
$105,600.00 |
$0.00 |
$105,600.00 |
|
Review functional specifications |
$0.00 |
$3,200.00 |
$0.00 |
$3,200.00 |
$0.00 |
$3,200.00 |
|
Identify modular/tiered design parameters |
$0.00 |
$3,200.00 |
$0.00 |
$3,200.00 |
$0.00 |
$3,200.00 |
|
Assign development staff |
$0.00 |
$3,200.00 |
$0.00 |
$3,200.00 |
$0.00 |
$3,200.00 |
|
Develop code |
$0.00 |
$48,000.00 |
$0.00 |
$48,000.00 |
$0.00 |
$48,000.00 |
|
Developer testing (primary debugging) |
$0.00 |
$48,000.00 |
$0.00 |
$48,000.00 |
$0.00 |
$48,000.00 |
|
Development complete |
$0.00 |
$0.00 |
$0.00 |
$0.00 |
$0.00 |
$0.00 |
|
Testing |
$0.00 |
$112,000.00 |
$0.00 |
$112,000.00 |
$0.00 |
$112,000.00 |
|
Develop unit test plans using product specifications |
$0.00 |
$12,800.00 |
$0.00 |
$12,800.00 |
$0.00 |
$12,800.00 |
|
Develop integration test plans using product specifications |
$0.00 |
$12,800.00 |
$0.00 |
$12,800.00 |
$0.00 |
$12,800.00 |
|
Unit Testing |
$0.00 |
$48,000.00 |
$0.00 |
$48,000.00 |
$0.00 |
$48,000.00 |
|
Review modular code |
$0.00 |
$16,000.00 |
$0.00 |
$16,000.00 |
$0.00 |
$16,000.00 |
|
Test component modules to product specifications |
$0.00 |
$6,400.00 |
$0.00 |
$6,400.00 |
$0.00 |
$6,400.00 |
|
Identify anomalies to product specifications |
$0.00 |
$9,600.00 |
$0.00 |
$9,600.00 |
$0.00 |
$9,600.00 |
|
Modify code |
$0.00 |
$9,600.00 |
$0.00 |
$9,600.00 |
$0.00 |
$9,600.00 |
|
Re-test modified code |
$0.00 |
$6,400.00 |
$0.00 |
$6,400.00 |
$0.00 |
$6,400.00 |
|
Unit testing complete |
$0.00 |
$0.00 |
$0.00 |
$0.00 |
$0.00 |
$0.00 |
|
Integration Testing |
$0.00 |
$38,400.00 |
$0.00 |
$38,400.00 |
$0.00 |
$38,400.00 |
|
Test module integration |
$0.00 |
$16,000.00 |
$0.00 |
$16,000.00 |
$0.00 |
$16,000.00 |
|
Identify anomalies to specifications |
$0.00 |
$6,400.00 |
$0.00 |
$6,400.00 |
$0.00 |
$6,400.00 |
|
Modify code |
$0.00 |
$9,600.00 |
$0.00 |
$9,600.00 |
$0.00 |
$9,600.00 |
|
Re-test modified code |
$0.00 |
$6,400.00 |
$0.00 |
$6,400.00 |
$0.00 |
$6,400.00 |
|
Integration testing complete |
$0.00 |
$0.00 |
$0.00 |
$0.00 |
$0.00 |
$0.00 |
|
Training |
$0.00 |
$102,400.00 |
$0.00 |
$102,400.00 |
$0.00 |
$102,400.00 |
|
Develop training specifications for end users |
$0.00 |
$9,600.00 |
$0.00 |
$9,600.00 |
$0.00 |
$9,600.00 |
|
Develop training specifications for helpdesk support staff |
$0.00 |
$9,600.00 |
$0.00 |
$9,600.00 |
$0.00 |
$9,600.00 |
|
Identify training delivery methodology (computer based training, classroom, etc.) |
$0.00 |
$6,400.00 |
$0.00 |
$6,400.00 |
$0.00 |
$6,400.00 |
|
Develop training materials |
$0.00 |
$48,000.00 |
$0.00 |
$48,000.00 |
$0.00 |
$48,000.00 |
|
Conduct training usability study |
$0.00 |
$12,800.00 |
$0.00 |
$12,800.00 |
$0.00 |
$12,800.00 |
|
Finalize training materials |
$0.00 |
$9,600.00 |
$0.00 |
$9,600.00 |
$0.00 |
$9,600.00 |
|
Develop training delivery mechanism |
$0.00 |
$6,400.00 |
$0.00 |
$6,400.00 |
$0.00 |
$6,400.00 |
|
Training materials complete |
$0.00 |
$0.00 |
$0.00 |
$0.00 |
$0.00 |
$0.00 |
|
Documentation |
$0.00 |
$100,800.00 |
$0.00 |
$100,800.00 |
$0.00 |
$100,800.00 |
|
Develop Help specification |
$0.00 |
$2,400.00 |
$0.00 |
$2,400.00 |
$0.00 |
$2,400.00 |
|
Develop Help system |
$0.00 |
$36,000.00 |
$0.00 |
$36,000.00 |
$0.00 |
$36,000.00 |
|
Review Help documentation |
$0.00 |
$7,200.00 |
$0.00 |
$7,200.00 |
$0.00 |
$7,200.00 |
|
Incorporate Help documentation feedback |
$0.00 |
$4,800.00 |
$0.00 |
$4,800.00 |
$0.00 |
$4,800.00 |
|
Develop user manuals specifications |
$0.00 |
$4,800.00 |
$0.00 |
$4,800.00 |
$0.00 |
$4,800.00 |
|
Develop user manuals |
$0.00 |
$36,000.00 |
$0.00 |
$36,000.00 |
$0.00 |
$36,000.00 |
|
Review all user documentation |
$0.00 |
$4,800.00 |
$0.00 |
$4,800.00 |
$0.00 |
$4,800.00 |
|
Incorporate user documentation feedback |
$0.00 |
$4,800.00 |
$0.00 |
$4,800.00 |
$0.00 |
$4,800.00 |
|
Documentation complete |
$0.00 |
$0.00 |
$0.00 |
$0.00 |
$0.00 |
$0.00 |
|
Pilot |
$0.00 |
$23,200.00 |
$0.00 |
$23,200.00 |
$0.00 |
$23,200.00 |
|
Identify test group |
$0.00 |
$6,400.00 |
$0.00 |
$6,400.00 |
$0.00 |
$6,400.00 |
|
Develop software delivery mechanism |
$0.00 |
$0.00 |
$0.00 |
$0.00 |
$0.00 |
$0.00 |
|
Install/deploy software |
$0.00 |
$2,400.00 |
$0.00 |
$2,400.00 |
$0.00 |
$2,400.00 |
|
Obtain user feedback |
$0.00 |
$12,000.00 |
$0.00 |
$12,000.00 |
$0.00 |
$12,000.00 |
|
Evaluate testing information |
$0.00 |
$2,400.00 |
$0.00 |
$2,400.00 |
$0.00 |
$2,400.00 |
|
Pilot complete |
$0.00 |
$0.00 |
$0.00 |
$0.00 |
$0.00 |
$0.00 |
|
Deployment |
$0.00 |
$12,000.00 |
$0.00 |
$12,000.00 |
$0.00 |
$12,000.00 |
|
Determine final deployment strategy |
$0.00 |
$2,400.00 |
$0.00 |
$2,400.00 |
$0.00 |
$2,400.00 |
|
Develop deployment methodology |
$0.00 |
$2,400.00 |
$0.00 |
$2,400.00 |
$0.00 |
$2,400.00 |
|
Secure deployment resources |
$0.00 |
$2,400.00 |
$0.00 |
$2,400.00 |
$0.00 |
$2,400.00 |
|
Train support staff |
$0.00 |
$2,400.00 |
$0.00 |
$2,400.00 |
$0.00 |
$2,400.00 |
|
Deploy software |
$0.00 |
$2,400.00 |
$0.00 |
$2,400.00 |
$0.00 |
$2,400.00 |
|
Deployment complete |
$0.00 |
$0.00 |
$0.00 |
$0.00 |
$0.00 |
$0.00 |
|
Post Implementation Review |
$0.00 |
$19,200.00 |
$0.00 |
$19,200.00 |
$0.00 |
$19,200.00 |
|
Document lessons learned |
$0.00 |
$6,400.00 |
$0.00 |
$6,400.00 |
$0.00 |
$6,400.00 |
|
Distribute to team members |
$0.00 |
$6,400.00 |
$0.00 |
$6,400.00 |
$0.00 |
$6,400.00 |
|
Create software maintenance team |
$0.00 |
$6,400.00 |
$0.00 |
$6,400.00 |
$0.00 |
$6,400.00 |
|
Post implementation review complete |
$0.00 |
$0.00 |
$0.00 |
$0.00 |
$0.00 |
$0.00 |
|
Software development Completion |
$0.00 |
$0.00 |
$0.00 |
$0.00 |
$0.00 |
$0.00 |
Schedule Risk- The project manager fails to estimate the schedule of the entire project. The software developers fail to complete the software development in time; it can delay the entire project. The project can fail.
Budget Risk- The project manager may fail to estimate the budget for the CRM software development. Cost overruns can lead to failure of the project.
Operational Risk– Inappropriate process implementation can lead to failure, and this can lead to operational risks.
Technical Risk- the CRM software will mainly deal with the customers. The CRM software will evaluate the financial data of both the company and the customers.
Programmatic Risk- The project can run out of the fund. The sponsor of the project can make minor alterations or can change the project scope as a whole.
Recommendations to shorten the duration of the project
Gold Plating- The software developers focus on show off; they might add a flash at the login screen to make the software interface more stylish. However, it is a waste of time.
Sudden requirement growth- Issues that are not identified initially can lead to hurdles at the last minute and can lead to disaster. The project manager must think big and must anticipate the outcome of the project.
Turnover of employee- Employee turnover can lead to several problems. The project will get delayed. The new employees will take time to understand the project and the project scope.
Schedule Risk- The project manager is responsible for preparing the project plan. However, he might make mistakes. The project manager may wrongly guess the project activities’ time duration. The project manager can fail to track the resources; can fail to identify the complexities of the project. The probability of schedule risk is high. The schedule risk has a great impact, and it can lead to project failure. The client company and the developer company will suffer loss and loss of money.
Budget Risk- The project manager is responsible for fixing the project budget initially. The project manager can estimate the budget wrongly. The CRM project cost can overrun. The probability of the risk is high. The budget risk has a large impact. The project due to lack of budget can get halt or can fail.
Operational Risks- Operational Risks can incur due to several reasons. The project manager can fail to point out the priority conflicts; they may fail to resolve the responsibilities. The operational risks also occur due to inappropriate subject training, inappropriate training. The probability is moderate. The impact of the risk is moderate. The project performance suffers due to inappropriate project risks.
Technical Risk- The CRM software is associated with the customers. The employees will evaluate the financial data of the company and the bills of the customer. Due to the continuous requirements change the technical risk arises.
Programmatic Risk- The CRM development project can run out of the fund. The probability of this risk is moderate. The impact is huge. The project stakeholders will leave. The project will halt. This will lead to project failure ultimately. Thus Programmatic Risk impact is quite high.
Gold Plating Risk- The software developers develops the software. Sometimes they add flash to the login screen. The screen may look stylish. However, it is just the waste of time. The developers need to focus on the functionality of the software so that the employee can use the CRM software effectively. The probability of the risk is low, and the impact of the risk is low.
Sudden Requirement Growth Risk- The problems related to CRM software development may erupt at the last minute. The tester may find any issue with the CRM software. If the problem is major, then the software developer will have to make heavy changes. The probability of the risk is medium. The impact of the risk is medium.
Turnover of employee- An employee may fall sick. The employee may leave the organisation. The company will suffer due to the absence of the employee. The new employee will need to understand the code and the work progress, and only after that, he can proceed. Therefore, there is a risk the project will delay. The probability of the risk is medium, and the impact is medium.
To check whether the project is time-constrained
The project manager and the software company must be concerned about the three risks- Budget Risk, Schedule Risk and Operational Risk. The project manager must prepare the CRM software development project plan wisely. The project stakeholders must work responsibly and must work hard to deliver the software within time. If they fail, the client will be dissatisfied and may refuse to take the project. In that case, the project will fail. The project manager must prepare the budget plan and must make the budget ready. After that, they should start working on the project. If the project runs out of the budget, then they will face disaster. The project work will stop and eventually fail. Due to inappropriate subject training and inappropriate decision can lead to project failure. The project manager may fail to realise the project conflicts, and the operational mismanagement can lead to project failure.
|
Risk Event |
Likelihood |
Impact |
Detection Difficulty |
When |
|
Schedule Risk |
4 |
4 |
4 |
Start-up |
|
Budget Risk |
4 |
5 |
4 |
Start-up |
|
Operational Risk |
3 |
4 |
4 |
Post installation |
|
Technical Risk |
3 |
3 |
3 |
Post installation and installation |
|
Programmatic Risk |
2 |
3 |
4 |
Post installation |
|
Gold Plating Risk |
2 |
1 |
2 |
Post installation |
|
Sudden Growth Risk |
2 |
5 |
4 |
Installation |
|
Turnover of employee |
4 |
3 |
3 |
Post installation and Installation |
|
Likelihood |
5 |
|||||
|
4 |
Turnover of employee |
Schedule Risk |
Budget Risk |
|||
|
3 |
Technical Risk |
Operational Risk |
||||
|
2 |
Gold Plating Risk |
Programmatic Risk |
Sudden Growth Risk |
|||
|
1 |
||||||
|
1 |
2 |
3 |
4 |
5 |
||
|
Impact |
|
Red zone (major risk) |
|
|
Yellow zone (moderate risk) |
|
|
Green zone (minor risk) |
|
Risk factor |
Response |
Contingency plan |
Trigger |
Responsible person |
|
Schedule Risk |
The software developers miss the deadline and fail to deliver the project within stipulated deadline |
The project manager must make the plan, and the stakeholders must follow the plan appropriately |
The project manager must act responsibly and will have to push the software developers, testers to deliver the project on time |
Software developers, software tester |
|
Budget Risk |
The project’s cost can overrun, the project manager should always remain concerned about the budget of the project |
The project manager must prepare the budget plan wisely and must make the budget ready to use the resources |
The project manager must take into consideration every resource of the project and then spend accordingly |
Project manager |
|
Operational Risks |
Project manager if fails to realise the project conflicts, the CRM development project may fail. The project may fail due to the project mismanagement and inappropriate decision making and inappropriate training. Thus the project manager must realise the project risks, project priorities and must focus on smart decision making |
The project manager, as well as the project stakeholders, must act responsibly and must make smart decisions, provide quality training and realise the project risks |
The project manager must analyse the risks associated with the project; They must make effective decisions and must encourage the other stakeholders of the project to do the same |
The project manager and the stakeholders |
|
Technical Risk |
Technical Risk erupts due to continuous change in system requirements. The stakeholder must be clear with all the deliverables before proceed on to work otherwise he works will get delayed |
The stakeholders must conduct the partial and get it reviewed by the client and the senior officials. They should work only after the approval from the clients or senior approvals |
The project manager must monitor that the stakeholders are doing the partial work and getting it reviewed by the clients. The stakeholders must proceed with the approval; the project manager must manage the stakeholders |
Project stakeholders |
|
Programmatic Risk |
The project may run out of the fund; the project can thus suffer. The project manager must ensure that the project fund is ready and then they should initiate the project |
The project should always start calculating the budget and make money available for the project all the time. The project manager then should start working on the project |
The project manager must instruct the project stakeholders to progress on to the work if both the resource and the budget is available for the project |
Client |
|
Gold Plating Risk |
The software developer sometimes adds extra features to the software that is unnecessary. For this reason, a lot of time gets wasted. The software developers must not focus on adding features instead they focus on the features by which the company can be benefitted using the CRM software |
The software developer must work on improving the quality of the software. The CRM software must work fast and effective all the time |
The project manager must advise the software developers to focus on matters that needed the most. |
Software developers |
|
Sudden Requirement Growth Risk |
CRM software related issues can generate at the last time. The software developers then have to make heavy changes in the software |
Sudden growth risk can be handled with the assistance of the partial work submission. Then the partial work must be approved from the client’s end. In this way, the project risk can be mitigated |
The project manager must instruct the stakeholders to proceed on to work only after getting approval from the client’s end |
Client and Software developer |
|
Turnover of employee |
The CRM software development can get delayed due to the turnover of the employee. The new developer will need time to understand the code and work on it. Therefore, they must sign a contract with the developer that the developer cannot leave the enterprise until the project gets completed |
The project manager must prepare policies so that the employee currently working on the project cannot leave the project unfinished |
The project manager should suggest the employee’s staff to follow the rules and the guidance |
Project manager and stakeholders |
PERT analysis giving the project duration with a 95% probability of successful completion
|
List of Activities |
0 |
M |
P |
Pert Est. (µ) |
Std. Dev |
Variance (σ^2) |
|
Scope |
3.5 |
4 |
3 |
3.75 |
-0.08 |
0.01 |
|
Software Requirements |
11 |
14 |
12 |
13.17 |
0.17 |
0.03 |
|
Design |
12 |
20 |
15 |
17.83 |
0.50 |
0.25 |
|
Development |
30 |
35 |
25 |
32.50 |
-0.83 |
0.69 |
|
Testing |
50 |
62 |
53 |
58.50 |
0.50 |
0.25 |
|
Training |
55 |
58 |
50 |
56.17 |
-0.83 |
0.69 |
|
Documentation |
43 |
54 |
50 |
51.50 |
1.17 |
1.36 |
|
Pilot |
75 |
82 |
82 |
80.83 |
1.17 |
1.36 |
|
Deployment |
2 |
6 |
3 |
4.83 |
0.17 |
0.03 |
|
Post Implementation |
1 |
3 |
3 |
2.67 |
0.33 |
0.11 |
|
Mean |
32.17 |
0.22 |
0.28 |
|||
P [z = 0.95]
z = 0.8289
D = 0.8289 * 0.53 + 32.17 = 19.04 = 32.609
Desired project completion time = 32.609
References
Bass, J. M. (2016). Artefacts and agile method tailoring in large-scale offshore software development programmes. Information and Software Technology, 75, 1-16.
Brhel, M., Meth, H., Maedche, A., & Werder, K. (2015). Exploring principles of user-centered agile software development: A literature review. Information and Software Technology, 61, 163-181.
Carlo, J. L., Gaskin, J., Lyytinen, K., & Rose, G. M. (2014). Early vs. late adoption of radical information technology innovations across software development organizations: an extension of the disruptive information technology innovation model. Information Systems Journal, 24(6), 537-569.
Eichorn, F. L. (2017). Internal customer relationship management (IntCRM) a framework for achieving customer relationship management from the inside out. Management (open-access), 2, 1.
Franken, S., Kolvenbach, S., Prinz, W., Alvertis, I., & Koussouris, S. (2015). CloudTeams: Bridging the gap between developers and customers during software development processes. Procedia Computer Science, 68, 188-195.
Lesser, E., & Ban, L. (2016). How leading companies practice software development and delivery to achieve a competitive edge. Strategy & Leadership, 44(1), 41-47.
Olson, D. L., Johansson, B., & De Carvalho, R. A. (2015). Open source ERP business model framework. Robotics and Computer-Integrated Manufacturing.
Peres, A. L., Da Silva, T. S., Silva, F. S., Soares, F. F., De Carvalho, C. R. M., & Meira, S. R. D. L. (2014, July). AGILEUX Model: Towards a reference model on integrating UX in developing software using agile methodologies. In Agile Conference (AGILE), 2014 (pp. 61-63). IEEE.
Quirchmayr, T., Paech, B., Kohl, R., & Karey, H. (2017, February). Semi-automatic software feature-relevant information extraction from natural language user manuals. In International Working Conference on Requirements Engineering: Foundation for Software Quality (pp. 255-272). Springer, Cham.
Quirchmayr, T., Paech, B., Kohl, R., & Karey, H. (2017, February). Semi-automatic software feature-relevant information extraction from natural language user manuals. In International Working Conference on Requirements Engineering: Foundation for Software Quality (pp. 255-272). Springer, Cham.
Sakas, D., Vlachos, D., & Nasiopoulos, D. (2014). Modelling strategic management for the development of competitive advantage, based on technology. Journal of Systems and Information Technology, 16(3), 187-209.
Soltani, Z., & Navimipour, N. J. (2016). Customer relationship management mechanisms: a systematic review of the state of the art literature and recommendations for future research. Computers in Human Behavior, 61, 667-688.
Wynn, M., Turner, P., Banik, A., & Duckworth, G. (2016). The impact of customer relationship management systems in small business enterprises. Strategic Change, 25(6), 659-674.
Zowghi, D., da Rimini, F., & Bano, M. (2015, April). Problems and challenges of user involvement in software development: an empirical study. In Proceedings of the 19th International Conference on Evaluation and Assessment in Software Engineering (p. 9). ACM.
Order an Essay Now & Get These Features For Free:
Turnitin Report
Formatting
Title Page
Citation
Outline
