Overview 

 

Leading Agile is a market leader that uses systems first approach through agile transformation to helps large companies achieve their goals. The company uses a transformation management system called Navigator that contains data’s about companies to help measure their progress toward agility. 

For this project, the team will help analyze information that Leading Agile has collected during the transformation process and analyze the data to help the company visualize patterns that aren’t obvious based on existing reports in the Navigator application. The team will also give recommendations on how this type of analysis could be embedded into Navigator in the future. 

 

 

Project Team 

Project owner 

Leonard Greski 

 

Via Allison Boyle 

Team leader 

Oumar Balde 

​

Team members 

Jakeel Johnson 

Jjohn824@students.kennesaw.edu 

​

Maraki Aemero 

maemero@students.kennesaw.edu 

​

Oumar Balde 

obalde@students.kennesaw.edu

​

Kevin Knight 

kknigh68@students.kennesaw.edu 

Advisor / Instructor

​

Allison Boyle 

Facilitate project progress; advise on project planning and management. 

Aboyle10@kennesaw.edu 

Final Deliverables

1. Data Analysis

2. Explanatory Analysis Formed

3. Hypothesis formed

4. Results Visualized

5. Storyline Developed

6. Automation Opportunities Identified

Milestones

#1 - By 09/06/2022

• Data stored in a FileZilla repository

• Data dictionary explaining data elements/ features

• R code to read data and build data frames

• Scripts used to clean the data (as needed)

• Basic descriptive statistics for features of interest

#2 - By 09/20/2022

• Exploratory visualizations/analyses

• List of hypotheses to be tested, including null and alternate hypotheses

• List of features needed to test the hypotheses

#3 - By 10/04/2022

• Analyses that test the hypotheses

• List of inferences made from the hypothesis tests

#4 - By 10/18/2022

• Reports / graphics illustrating the hypothesis tests & inferences

#5 – By 11/01/2022

• Presentation / report that tells a business story

#6 – By 11/15/2022

• Recommendations for how one might automate the analysis and embed it into the Navigator software.

Future milestone meetings date/time

09/06/2022 Tuesday 3:00pm (Jakeel, Markari, Oumar, Kevin)

09/20/2022 Tuesday 3:00pm (Jakeel, Markari, Oumar, Kevin)

10/04/2022 Tuesday 3:00pm (Jakeel, Markari, Oumar, Kevin)

10/18/2022 Tuesday 3:00pm (Jakeel, Markari, Oumar, Kevin)

11/01/2022 Tuesday 3:00pm (Jakeel, Markari, Oumar, Kevin)

11/15/2022 Tuesday 3:00pm (Jakeel, Markari, Oumar, Kevin)

​

Collaboration and Communication Plan

 

• Always try their best to share the work equally and everyone must be open to compromise.

 

•  The job assigned to each group must be or each member must do his best to be at 70% of his task a week before the deliverables.

 

• Always ask for help when you know you will be late to complete your task or cannot do the work.

 

•  Each group member must always keep up with the discussion in the group chat or replied on time avoiding ghosting the other for days.

 

•  Weekly meetings are on Thursday at 8:00pm. Each group member should respect the meeting time we agreed upon or inform in time for the absence.

 

•  Always come prepared to the meetings and share something. Everyone should contribute and speak.

 

•  The team leader will report weekly progress updates via email to Allison Boyle every Friday by 3:00 pm.

•  The team will be using GroupMe for communication and file sharing. Microsoft teams will be used for meetings.

 

 

Project Schedule and Tasks Planning

See the Gantt chart file attached. 

[Other planning] 

See the Gantt chart file attached.