° Sesión 04–09–2026 – PC GEPROYTI 2026 III ONLINE LAT

Introduction and Greetings

Opening Remarks

• The session begins with greetings among participants, establishing a friendly atmosphere as they prepare to start the meeting.

• The speaker expresses happiness to reconnect with the group on a Friday evening, acknowledging the challenges of the week.

• Acknowledgment of sacrifices made by participants in terms of family and social life due to their commitment to this session.

Participant Engagement

• The speaker encourages participants to share their photos for better recognition, noting that there are only three women in the class.

• An invitation is extended for any participant who hasn't introduced themselves yet, highlighting the small size of the group.

Weather Discussion

Climate Conditions

• Juan Carlos shares his experience regarding high temperatures in Cancún, discussing current weather conditions.

• A discussion ensues about how heat affects telecommunications infrastructure, particularly data centers and servers.

Technical Infrastructure Insights

Data Center Management

• Explanation of climate control measures in hotels' IDFs (Intermediate Distribution Frames), emphasizing air conditioning systems for data centers.

• Mention of dehumidifiers used in IDFs to manage humidity levels during rainy seasons.

Project Overview Presentation

Project Introduction

• Carlos introduces a project focused on implementing a regional observatory for vulnerable populations under Cusco's government development management.

Project Details

• Key details include 13 provinces and 116 districts within Cusco, along with an initial budget of 180,000 soles allocated for the project.

Methodology and Implementation Strategy

Predictive Model Approach

• The project employs a predictive methodology with predefined modules aimed at accelerating development timelines.

Technical Specifications

• Description of web platform architecture utilizing containers (K3S), indicating that it will be hosted within government data centers.

Objectives and Functionality

General Objective

• The main goal is to implement an observatory tool that registers, processes, visualizes information related to vulnerable populations.

Access Control

• Information access will be restricted; public dashboards will display non-nominal aggregated data only.

Development Phases

Project Milestones

• Outline includes design analysis, implementation phases, testing procedures, and final deployment steps necessary for project completion.

Team Composition

Professional Roles

• Identification of key team members including project leaders and specialists responsible for various aspects such as programming and security.

Stakeholder Involvement

Governance Structure

• Emphasis on collaboration between local governments and functional units crucial for maintaining updated information within the system.

Challenges Faced

Institutional Coordination Issues

• Discussion about difficulties coordinating meetings among stakeholders which can delay progress due to varying availability.

Risk Management Strategies

Identifying Risks

• Highlighting potential risks associated with contractual deadlines which could lead to penalties if not adhered to strictly.

Security Concerns

Data Protection Measures

• Addressing vulnerabilities related to sensitive data handling especially concerning minors or vulnerable groups involved in the project.

Benefits Realization

Long-term Advantages

• Discusses how real-time information access through this platform can reduce reliance on costly consultancies traditionally needed for social projects.

Success Criteria

Evaluation Metrics

• Outlining success criteria based on timely milestone achievements and operational functionality post-deployment training sessions conducted effectively.

Conclusion & Next Steps

Final Remarks

• Closing remarks emphasize importance of stakeholder engagement throughout all phases ensuring successful implementation while addressing any outstanding questions from participants regarding financial aspects or documentation requirements.

Project Management Fundamentals

Introduction to Project Initiation

• A group of high-level stakeholders from various sectors (company, regional government, transport, finance) decides which projects to pursue, marking the start of project management.

• The first step in project management is creating a project charter that outlines what will be done, although complexities and budget considerations may not be fully clear at this stage.

Understanding the Project Charter

• The project charter should clarify whether the approach is predictive, hybrid, or agile; this influences how detailed the charter can be.

• The charter serves as a commitment between the project manager and sponsors regarding deliverables and conditions; it’s distinct from a contract with third parties.

Managing Changes in Projects

• In hybrid projects, it's crucial to define which aspects can change; for example, switching from a warehouse system to an ERP system constitutes a fundamental shift rather than just a modification.

• Effective communication about changes helps avoid conflicts and misunderstandings among stakeholders.

Agile Project Charters

• An agile project charter includes an overall vision and lists of stakeholders and risks but does not delve into details until after initial discussions are held.

• After establishing the charter, detailed planning occurs where specific requirements are validated based on stakeholder input.

Importance of Planning

• If external contracts are involved, experience becomes critical for fulfilling commitments accurately; miscommunication can lead to scope creep.

• Budget overruns often occur due to changing requirements during projects; clarity in initial agreements is essential to prevent dissatisfaction later on.

Transitioning from Charter to Planning

• Once the project charter is established and all points identified, detailed planning begins based on whether the approach is hybrid, predictive or agile.

• Planning involves validating expectations with stakeholders and understanding their influence on project outcomes.

Common Misconceptions About Planning

• Some believe that avoiding planning leads to better outcomes due to lower expectations; however, this often results in failure when unforeseen issues arise.

• Proper planning allows for contingencies such as late arrivals or equipment failures by anticipating potential problems ahead of time.

Defining Scope Clearly

• It’s vital to distinguish between product scope (features of what is being built) versus project scope (how it will be delivered).

• Specific characteristics must be defined early on for both product and project scopes to ensure alignment with stakeholder needs.

Gathering Requirements Effectively

• Collecting requirements goes beyond asking users what they want; it requires understanding their underlying needs and motivations.

• Engaging multiple stakeholders ensures diverse perspectives are considered when defining requirements for technology projects.

Managing Expectations

• To effectively manage expectations, ask deeper questions about why certain features are needed rather than simply accepting surface-level requests.

Conclusion: Importance of Requirement Management

• A robust plan for managing requirements prevents misunderstandings that could derail projects. Clear communication about expectations leads to successful outcomes.

Project Management Approaches: Predictive, Agile, and Hybrid

Understanding Project Closure and Initiation

• The discussion begins with the idea of closing a project and initiating a new one based on clearer objectives. This can be predictive or hybrid in nature.

• In agile methodologies, there are no strict schedules or budgets; instead, there is a flexible approach to managing projects that allows for ongoing adjustments.

Engaging Participants in Discussion

• The speaker encourages participation through chat to gauge what participants observe in visual prompts presented during the session.

• Various interpretations arise from the visuals shared, highlighting how perspectives differ among individuals.

Perception and Interpretation

• The conversation shifts to how people perceive images differently based on their backgrounds and experiences. This reflects broader themes of understanding in technology.

• Information technology professionals often operate at an abstract level that may not resonate with non-tech stakeholders like accountants or lawyers.

Communication Challenges in Projects

• It’s emphasized that projects are created for others, who may have different expectations than those involved in the technical aspects.

• Different interpretations of visuals (like animals seen by participants) illustrate how subjective perception can lead to misunderstandings.

Perspectives Shape Understanding

Subjectivity in Observations

• The speaker notes that both perspectives (e.g., seeing a frog vs. a horse) are valid but depend on individual viewpoints shaped by personal history.

• IT professionals possess unique skills that may not align with stakeholder expectations, leading to potential conflicts during project implementation.

Managing Stakeholder Expectations

• When developing software or systems, it’s crucial to ensure stakeholders understand the solutions being provided; otherwise, they may resist changes during implementation.

Clarifying Requirements Through Collaboration

Importance of Clear Communication

• A metaphorical example illustrates differing views (six vs. nine), emphasizing the need for clarity when discussing project requirements among diverse stakeholders.

Engaging Non-Tech Stakeholders

• Many stakeholders might struggle with technical jargon; thus, explaining processes rather than technical details can facilitate better understanding.

Utilizing Process Diagrams for Clarity

Visual Tools for Understanding

• Walter suggests using process diagrams as they help various departments grasp their roles within larger projects without needing deep technical knowledge.

Digital Transformation vs. Simple Digitization

Differentiating Project Types

• The speaker distinguishes between digital transformation (creating new tools or applications that didn’t exist before), versus simple digitization (converting existing processes into digital formats).

Validating Expectations Through Dialogue

Gathering Requirements Effectively

• To validate stakeholder expectations effectively, engaging directly with users is essential—this includes interviews and focus groups to clarify needs and desires.

Technical vs. Managerial Perspectives

Bridging Gaps Between Teams

• , which cater primarily to system developers versus managerial approaches focusing on stakeholder engagement is critical for successful project management.

Techniques for Requirement Gathering

Diverse Methods for Engagement

• Various techniques such as interviews, focus groups, workshops, surveys etc., should be employed depending on client needs and context to gather comprehensive requirements effectively.

Aligning Stakeholder Expectations

Unifying Diverse Views

• When working with multiple stakeholders like university deans who have varying expectations about digital transformation initiatives it's vital to unify these views into actionable requirements.

Defining Specific Needs

Clarifying Requirements Further

• It's important to specify exactly what each stakeholder wants from a project—whether it’s speed or features—to avoid conflicting demands later down the line.

Complexity of Systems Development

Balancing Features Against Reality

• Assembling requirements must consider practical limitations while ensuring all voices are heard so that final deliverables meet collective expectations without overpromising capabilities.

Managing Requirements with Project Model Canvas

Introduction to Project Model Canvas

• The Project Model Canvas serves as a tool for managing requirements, simplifying the process to encourage collaborative and positive participation among stakeholders.

• As the project evolves through multiple versions, consensus is reached on benefits and requirements, ensuring alignment with stakeholder expectations.

Deliverables and Stakeholder Engagement

• Clarification of deliverables is essential; they evolve throughout the project lifecycle, requiring input from various experts across departments.

• Engaging key stakeholders ensures that their perspectives are integrated into the project vision, validating assumptions and aligning objectives.

Importance of Trust and Validation

• Building trust with stakeholders like Don Pedro and Lenin is crucial for validating the project's charter within budgetary constraints.

• Misunderstandings can lead to scope creep; clear communication about agreements helps prevent future conflicts over resources.

Requirement Traceability Matrix

• Once clarity on requirements is achieved, transitioning to a requirement traceability matrix becomes vital for tracking changes in a predictive or hybrid model.

• This matrix links products to stakeholder needs while ensuring that SMART objectives guide project deliverables.

Work Breakdown Structure (WBS)

• The Work Breakdown Structure (WBS), or EDT in Spanish, breaks down projects into manageable components, facilitating easier oversight and control.

• A hierarchical structure allows for detailed identification of all necessary elements within a project without focusing solely on phases or stages.

Packages of Work

• Each package of work represents specific tasks that can be measured in terms of time and cost, allowing for effective management.

• These packages must be validated by responsible parties to ensure accountability throughout the project's execution.

Planning and Execution Strategies

• Effective planning involves creating a network diagram that outlines task dependencies—both sequential and parallel—to optimize resource allocation.

• Understanding critical paths within these diagrams helps identify which tasks directly impact overall project timelines.

Conclusion: Ensuring Project Success

• By integrating all elements—from requirement gathering through WBS creation—project managers can enhance their ability to meet deadlines while staying within budget constraints.

Project Management Insights and Strategies

Understanding Resource Allocation

• Discussion on project management reveals the need for accurate resource allocation, highlighting a shift from initial estimates (35 to 45 days) due to better project management practices.

• Emphasis on avoiding overworking teams by recognizing the importance of realistic timelines and resource needs rather than pushing for unrealistic work hours.

Strategic Planning in Projects

• The speaker illustrates how to analyze costs effectively when adding resources, suggesting that junior team members can be assigned tasks to optimize budget without compromising quality.

• A metaphorical comparison is made between sports strategy and project planning, emphasizing the importance of assigning roles based on team strengths.

Tools and Techniques for Effective Management

• Introduction of various tools such as requirement matrices and network diagrams that aid in creating structured project schedules.

• The discussion transitions into predictive versus agile methodologies, stressing that clear deliverables are essential for effective project management.

Risk Management Considerations

• The necessity of identifying risks early in the planning process is highlighted, with examples including server failures or unexpected events impacting timelines.

• It’s suggested that large projects should be divided into smaller teams or functionalities to manage complexity more effectively.

Importance of Team Dynamics

• Recognition that team performance relies heavily on accurately assessing individual capabilities and aligning tasks accordingly.

• The concept of commitment within high-performance teams is discussed, underscoring the balance between realistic goals and personal limits.

Planning Methodologies Explained

• Overview of PMBOK's 40 processes categorized into initiation, planning, execution, monitoring/control, and closure; stressing practical application over rigid adherence to formats.

• Mention of various software tools like Primavera or Monday.com used for managing hybrid projects effectively.

Financial Implications in Project Planning

• Discussion about financial considerations during planning phases emphasizes understanding cost implications tied to risk management strategies.

Final Thoughts on Project Execution

• Concluding remarks stress the significance of thorough risk assessment integrated into overall project planning to avoid costly mistakes later on.

• A reminder that poor planning can lead to severe consequences such as increased costs or legal issues.

Engaging with Stakeholders

• Importance placed on stakeholder engagement throughout the project lifecycle; ensuring their expectations align with deliverables is crucial for success.

Learning from Experience

• Encouragement towards learning through trial and error during training sessions; real-world applications highlight potential pitfalls in project management practices.

This markdown file encapsulates key insights from the transcript while adhering strictly to your formatting guidelines. Each bullet point includes a timestamp link for easy reference back to specific moments in the discussion.