UBC-MDS / Telco_Customer_Churn_Prediction_Group12

Data Analytics project performed by Group 12 for DSCI 522
MIT License
2 stars 7 forks source link

Milestone 2 feedback #62

Open andytai7 opened 2 years ago

andytai7 commented 2 years ago

Dear group 12,

You guys have made improvements! Great job! Below highlight some feedback for milestone 2. In addition, things under Suggestions: should be taken as suggestions and do not affect your mark.

Expectations: Mechanics

Comments Zihan Zhou has two commits, and this is not balanced with the other students.

Project organization and documentation expectations: Mechanics

Comments Why are there two repeated slides "telco_churn_pipeline"

There are also two reports, that are duplicated.

Project organization and documentation expectations: Reasoning

Comments Please explain what Churn is in laymen terms.

"We first looked at the distribution of target (Churn) class to understand class imbalanced. " What do you mean by understand? What sort of class balancing strategies are you implementing? Even if there is no strategy, the group brushes it off after presenting the classes.

"Here, it was observed that there is high positive correlation between Tenure and Total Charges" After knowing the positive correlation what did you do about it? and why?

It is confusing why there are metrics for the accuracy category? Just keep Churn if that is your targeted predicted outcome.

Suggestions: "We used a logistic regression algorithm to build a classification model to predict which customers are likely to churn from their telecommunications company." Please try to justify the use of logistic regression in your rationale.

Overall great job!

Anupriya-Sri commented 2 years ago

Dear @andytai7,

We appreciate your efforts in reviewing this project and thank you for your feedback. Please find below our response to your comments:

_Why are there two repeated slides "telco_churnpipeline"

One of the slide had the editable version for future changes and other was an image to be included in any report. However, we have taken your feedback and moved the editable version to /src/ and retained the final image in /docs/ (https://github.com/UBC-MDS/Telco_Customer_Churn_Prediction_Group12/commit/114c21e324f0443ea24ffa421f4e63d2d0a3515b)

There are also two reports, that are duplicated.

The second report was a pandas profile report created as a part of EDA. However, we have already covered all this information in the eda_notebook, so, we are deleting this file. (https://github.com/UBC-MDS/Telco_Customer_Churn_Prediction_Group12/commit/06b746ac29611a52f09852ff61a8c5aabde7e1fd)

Project organization and documentation expectations: Reasoning Noted. We have updated the final report to make the highlighted section more clear to readers.

Once again, we thank you for your inputs towards improving the quality of this project.

andytai7 commented 2 years ago

Thank you @Anupriya-Sri!