Project Management

Please login or join to subscribe to this thread

How do you navigate unexpected data challenges in your projects?

linkedin twitter facebook   Artificial Intelligence  
avatar
Claudia Alcelay
PMI Team Member
Learning & Innovation Research Manager| Project Management Institute (PMI) Spain
Data quality and quantity is particularly important as we think about leveraging AI on projects. Considerations include the diversity and comprehensiveness of the data that is available to us. 
 
Have you ever encountered unexpected challenges or pitfalls while using data in your projects? How did you navigate the situation and find a resolution? 
Sort By:
< 1 ... 21 22 23 24 25 26 27 28 29 30 31 ... 42 >
avatar
Anonymous
Variability in how in-house data were generated / collected has led to issues, currently working to put in processes that help us standardize these.
avatar
Erick A. Candanedo S. Lead Researcher| PMRD Program
Relaying in continuous improvement of data with analysis and treatments is the best way to manage data quality.
avatar
Erick A. Candanedo S. Lead Researcher| PMRD Program
Relaying in continuous improvement of data with analysis and treatments is the best way to manage data quality.
avatar
Francis Irudayaraj Director| PROHRD HCIM Kuwait, Ha, Kuwait

Dear Claudia,
Thank you for your question regarding navigating unexpected data challenges in our projects. At PRORD Human Capital and Innovation Management, we recognize the critical importance of data quality and quantity, especially when leveraging AI. Here’s how we handle such challenges:
Navigating Unexpected Data Challenges
1. Root Cause Analysis
When we encounter unexpected data issues, our first step is to conduct a thorough root cause analysis. This helps us identify the source of the problem, whether it’s due to data collection methods, data entry errors, or inconsistencies in data sources.
2. Data Cleaning and Preprocessing
We implement robust data cleaning and preprocessing steps to handle inconsistencies and ensure the data is accurate and reliable. This includes removing duplicates, handling missing values, and standardizing data formats.
3. Backup Plans
Maintaining backup data sources and alternative datasets is crucial. This ensures continuity and allows us to switch to alternative data sources if the primary data is compromised.
4. Expert Consultation
Engaging data experts and stakeholders is essential. Their insights help us understand the nuances of the data and develop effective solutions to address any issues.
5. Agile Methodology
We use agile practices to adapt quickly to changes and iterate solutions. This flexibility allows us to respond promptly to data challenges and make necessary adjustments.
6. Continuous Monitoring
Setting up automated monitoring systems helps us detect and address data issues early. Continuous monitoring ensures that any anomalies are identified and resolved promptly.
7. Documentation
Maintaining thorough documentation of data challenges and solutions is vital. This helps us track issues and resolutions, providing valuable insights for future projects.
Real-World Example
In one of our recent projects, we faced a significant challenge due to a shortage of high-quality data. This delayed the project rollout. To overcome this, we identified key data owners and secured permissions to access their datasets. This collaborative effort significantly increased our data pool, enabling us to successfully develop and launch the project.
By implementing these strategies, we ensure that our projects remain on track and deliver the desired outcomes, even when faced with unexpected data challenges.
Best regards,
Francis
PRORD Human Capital and Innovation Management

avatar
Phyllis Simpson Indianapolis, In, United States
In projects I consider impact and probability, ability to provide canned options, and offer standardized naming conventions policies and procedures.
avatar
Julia Given Program Manager| Charleston Area Medical Center Given, Wv, United States
Feb 01, 2024 4:13 PM
Replying to Verónica Elizabeth Pozo Ruiz
...
The main pitfalls that we can encounter when working with large amounts of data are inaccuracies, incoherency, and duplicated or outdated data. It's appropriate to use Data Quality Management Software to identify and correct these issues, and also monitor and synchronize data across the company, keeping database quality perfect.
Our jobs would be a lot easier if this is all that was required. There are still data fiefdoms out there whose management teams that have to be educated on scrubbing/normalizing data (old terms; same problem).
avatar
Edward Davis Project Manager| Inspector| None Groveport, Oh, United States
Jan 13, 2024 3:47 AM
Replying to Nikita Jha
...
In my previous project, the objective was to reduce obsolescence for database technologies across the globe aka many regions. The timeframe for communication with immense amount of data took two weeks cycle for response and plan of action. However the data kept growing as many assets were not listed in a particular region as API failed to retrieve information at the right time. Hence I took that region as a subset project with dedicated resources and fast tracked to bring the region at par with other regions. It was immensely challenging but at the end it was rewarding in terms of achievement and stakeholders appreciation.
Keeping it very simple initially: Assure that the data resources are accurate- companies can vastly vary on how their data is pulled and distributed. Review lessons learned from prior projects, strong proactive risk analysis, and contingency plans.
avatar
YULITH MARTINEZ Colombia
In several projects data cleansing has been necessary, and it has been carried out both at a technical level and with the participation of the business areas or data owners, normally in parallel to the execution of the main project. It is very important to achieve successful results that the data is clean and accurate.
avatar
Anonymous
I would consult, review, evaluate, and collaborate with all affected on the best way to handle the situation.
avatar
Anonymous
Depends on which data we are referring to. If we are looking at the data generated by the team as part of the project management activities irrespective of the type of Project then my experience is says that as a Project Manager I always ensured to rectify the data on a regular basis as this would impact the analytical reports we can generate for Sr. Mgmt review.

If the data inconsistencies is about AI application then as per my understanding it is a technical work.
< 1 ... 21 22 23 24 25 26 27 28 29 30 31 ... 42 >

Please login or join to reply

Content ID:
ADVERTISEMENTS

Waiting for the time when I can finally say that this has all been wonderful but now I'm on my way.

- Phish

ADVERTISEMENT

Sponsors