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

Introduction and Greetings

Opening Remarks

• The speaker greets the audience warmly, expressing excitement to share insights on a Wednesday evening in September.

• Interaction with participants begins, with greetings exchanged among attendees including Fernando, Lenin, and David.

Weather Discussion

• The weather in Lima is described as unpredictable, fluctuating between sunny and cold conditions.

• Participants share their experiences of recent weather changes, highlighting unusual patterns like rain after a period of sunshine.

Project Updates from Participants

Group Work Progress

• Fernando updates on his group's progress regarding the constitution act for their project, indicating they have chosen an interesting topic to discuss later.

• Discussion about various projects among participants reveals diverse fields of interest and learning opportunities.

Meril's Project Insights

• Meril's project focuses on remote attendance marking and electronic document signing within her company that provides cleaning services.

Upcoming Plans and Training Sessions

Future Engagements

• Fernando plans to visit Arequipa in three weeks for training sessions related to new hospital equipment.

• He explains the nature of his upcoming training work involving laptops and printers at a newly constructed hospital.

Personal Background Sharing

Educational Journey

• Fernando shares that he studied his undergraduate degree in Lima after moving there due to his father's job transfer from Arequipa.

Class Participation Reminder

Importance of Engagement

• The speaker emphasizes the need for all participants to upload their photos for better interaction during class sessions.

Learning Objectives

Focus on Practical Learning

• The session aims not only at theoretical knowledge but also practical insights into each participant's projects which will enhance professional skills.

Introduction to Project Management Concepts

Understanding Project Charter

• The speaker introduces key concepts in project management focusing on the importance of creating a project charter or acta de constitución as foundational documentation.

Terminology Clarification

• Different terms used across organizations for similar documents are discussed; emphasis is placed on consistency within teams regarding terminology.

Document Purpose

• The project charter serves as a mutual agreement outlining roles, responsibilities, and objectives between teams involved in a project.

Legal Considerations

• It’s noted that while legal contracts may accompany charters, the focus should be on collaborative goals rather than punitive measures.

Approach Selection

• Teams must decide whether to adopt predictive or agile methodologies based on project complexity and desired outcomes.

Components of the Project Charter

Customization Options

• The structure of the project charter can be tailored according to specific needs; larger projects may require more detailed documentation compared to smaller ones.

Presentation Guidelines

• Participants are instructed on how to present their projects succinctly without reading verbatim from documents during class presentations.

Evaluation Criteria

• Clear criteria are established for evaluating group presentations based on engagement with content rather than rote recitation.

Group Presentations Begin

Overview of Projects

• Meril introduces her group’s ongoing project at SIS focused on developing an application aimed at improving operational efficiency through digital solutions.

Challenges Addressed

• Key issues such as delays in document processing and compliance risks due to reliance on paper-based systems are highlighted as motivations behind this initiative.

Goals Outlined

• Specific objectives include designing an app for attendance tracking and document management aimed at enhancing user experience by reducing paperwork significantly.

Assumptions for Mobile Application Development

Key Assumptions

• The operational staff is assumed to have smartphones necessary for downloading the application and marking attendance.

• It is presumed that the electronic signature provider, Guatana, maintains its certification with Indepc.

• Connectivity issues can be mitigated through offline mode; budget approval from management is essential for project continuity.

Restrictions and Exclusions

• The application will not include payroll functionalities or calculations; no corporate phones are provided to operational staff.

• There will be no integrations with exclusive client systems or biometric clock implementations.

Application Features and Requirements

Core Features

• Attendance registration utilizes geolocation to confirm personnel presence at client sites.

• Offline mode has been developed, along with integration capabilities with Watana for digital signatures.

User Profiles

• Three distinct user profiles are established: operational worker, field supervisor, and administrative management.

Identified Risks in Implementation

High-Level Risks

• Resistance to change poses a significant risk; efforts are ongoing since 2023 to address this issue effectively.

• A major concern includes intermittent connectivity affecting app usage among staff without personal devices.

Additional Risks

• Low digital literacy among older employees (ages 35–55), necessitating increased training efforts.

• Legal ambiguities regarding employer responsibilities when using the app have been discussed extensively with legal advisors.

Project Timeline and Development Phases

Development Milestones

• Initial development began in September 2023 after market research on existing applications in Peru and abroad.

• A pilot plan commenced in March-April 2024 with administrative personnel using an APK version of the app.

Future Plans

• By December 2026, the goal is to have 1000 active users utilizing all modules of the application effectively.

Budget Considerations

Financial Overview

• The budget primarily covers salaries for a team of four developers working directly on the project without third-party involvement.

• Costs associated with Watana's services will only be incurred once electronic signatures begin being utilized later in September.

Stakeholder Engagement

Key Stakeholders

• The general manager serves as the main sponsor of the project, emphasizing improved attendance tracking for payroll purposes.

• Various departments including HR, legal, accounting, operations, and commercial teams are involved in managing different aspects of the project.

Agile Project Management Approach

Agile Methodology

• The project is viewed as agile due to its adaptability over time rather than following a strict long-term plan.

• Emphasis on flexibility allows adjustments based on evolving requirements throughout development phases.

Hybrid Project Characteristics

Defining Hybrid Nature

• While much documentation exists suggesting predictability, it remains fundamentally agile due to variable elements influencing progress.

• A hybrid approach may apply if clear end dates and deliverables are established while allowing iterative improvements during development cycles.

Management of Stakeholders in Projects

Understanding Stakeholder Management

• A stakeholder management document is essential, detailing who the stakeholders are, their preferences, expectations, and power dynamics.

• Regular reviews of stakeholder interest should be conducted every few months to ensure effective engagement and management strategies.

• Stakeholders can include not only individuals but also groups like programmers and primary users involved in the project.

Group Presentation Overview

• Walter Torres introduces his group (Group 5), noting participation from six out of eight members due to work commitments.

• The group has selected a project named "Miniso" after discussing their skills and roles collectively.

Project Details: Miniso

Project Background

• The project involves creating an act of constitution for Miniso, which includes a list of stakeholders and other relevant documents.

• A PowerPoint presentation summarizes key aspects of the project while allowing for deeper exploration into the act of constitution later.

Current Challenges

• Currently, import processes at Miniso are manual and disorganized, leading to inefficiencies such as lack of centralized tracking and reliance on Excel sheets.

• Human errors in manual processes often result in data loss or incorrect information that delays decision-making by management.

Identified Problems and Project Objectives

Key Issues

• The importation department lacks a unified digital system for tracking shipments, resulting in significant operational challenges.

Project Goals

• The objective is to develop a web-based tracking system that integrates with existing ERP systems to streamline import processes.

System Development Scope

Features Included

• The initial module will cover product master data management, shipment tracking, cost liquidation automation, and reporting functionalities.

Limitations Defined

• No modifications will be made to the existing ERP; instead, interfaces will be created using flat files for data integration.

Team Structure and Roles

Team Composition

• Key team members include Emily Vargas (Sponsor), Carlos Ramos (IT Manager), Maria Pilar Solis (Analyst), among others responsible for various functions within the project.

Risk Assessment

Initial Risks Identified

• High risk associated with user availability due to manual tasks requiring physical presence at ports can lead to delays in operations.

Change Management Concerns

• Resistance from operational staff towards automation may hinder implementation; training is necessary to ease transitions into new workflows.

Milestones and Expected Outcomes

Deliverables Timeline

• Key milestones include kickoff meetings, approval stages for analysis/design phases followed by product master loading before moving onto shipment tracking features.

Anticipated Benefits

The expected outcome is a fully integrated web system that enhances real-time visibility over imports while reducing human error significantly.

Project Framework Overview

Methodology Employed

• The project follows a traditional predictive approach with defined scope from inception including fixed costs and established deliverables timelines.

Importance of Stakeholder Engagement

• Active involvement from all relevant departments such as logistics or finance is crucial during development phases to avoid misalignment on requirements or expectations.

Introduction and Group Participation

Initial Remarks

• The professor greets the group, confirming participation and encouraging a relaxed atmosphere during their meeting.

• Walter is instructed to stop sharing his screen, allowing César to take over for the presentation.

Project Overview

Project Focus

• César begins discussing the project, which addresses issues related to citizen security in San Juan de Lurigancho.

• The team collectively decided on developing a solution aimed at improving safety due to high crime rates in the district.

Project Details

Smartw SJL Initiative

• The project is named "Smartw SJL" and involves creating an integrated platform for community alert management.

• It will include a mobile application designed for residents of San Juan de Lurigancho, connecting them with local authorities through a monitoring center.

Technical Implementation

Cloud-Based Management

• The application will operate via cloud technology, enabling operators at the municipal monitoring center to receive alerts from citizens efficiently.

• A detailed description of the project's objectives includes reducing emergency response times significantly.

Methodological Approach

Hybrid Methodology

• The project adopts a hybrid methodology combining predictive elements with agile development practices for app creation.

• Emphasis is placed on deploying software that integrates seamlessly with existing infrastructure at the municipality's monitoring center.

Justification and Objectives

Addressing Local Needs

• The justification highlights that San Juan de Lurigancho has over one million inhabitants facing significant public safety challenges.

• Current emergency response times exceed 25 minutes; thus, the goal is to reduce this time to under 7 minutes through effective software integration.

Value Proposition

SMART Objectives

• Objectives are defined as Specific, Measurable, Achievable, Relevant, and Time-bound (SMART), focusing on operational efficiency and community engagement.

• Features like an SOS button within the app aim to enhance user experience while ensuring accountability through identity verification measures.

Timeline and Budget

Project Duration

• The project timeline is set for six months from initiation; key milestones are outlined for tracking progress effectively.

• A budget of $60,000 has been allocated covering all aspects of development including software integration and training costs.

Stakeholder Identification

Key Participants

• Stakeholders include developers, municipal authorities, end-users (residents), and external service providers who have varying expectations from the project.

• Each stakeholder's role is crucial in ensuring successful implementation and operation of the Smartw SJL initiative.

Risk Assessment

Identifying Challenges

• Risks such as browser compatibility issues or false alerts were identified along with mitigation strategies like mandatory user validation processes.

• GPS signal loss in certain areas poses another risk; solutions involve sending last known coordinates during outages.

Acceptance Criteria

Completion Standards

• Successful completion criteria include stable operation of both web console at control centers and mobile applications available on Google Play Store.

• A trial period ("marcha blanca") lasting 15 days will be implemented post-launch to ensure functionality before final acceptance by stakeholders.

Project Risk Assessment and Migration Strategy

Identifying Risks

• The project faces a medium probability risk of critical operation interruptions during the migration, with a high impact. A strategy includes conducting migrations outside of business hours and having a rollback plan in place.

• User resistance to the new interface is another identified risk, also with medium probability and impact. Training and support materials will be provided prior to the launch.

Assumptions and Constraints

• Key assumptions include having backups available and ensuring that the production database is verified before starting the migration. Infrastructure must meet technical requirements, with custom modules having accessible source code for updates.

• Constraints dictate that migration must occur during maintenance windows to minimize operational impact, ideally on weekends or outside working hours. The project does not account for new hardware acquisitions.

Project Constitution Document Overview

Project Goals

• The document serves as a constitution for the project focused on migrating ERP versions. It follows a traditional predictive approach.

• Measurable objectives are crucial; they should allow for clear assessment of success or failure through specific metrics.

Measurement Criteria

• Objectives should be quantifiable, such as completing an inventory analysis of compatibility with all installed custom modules, aiming for either 100% completion or zero errors post-migration.

Technical Considerations in Migration

Migration Timeline Discussion

• The proposed timeline for migration from version 15 to 18 spans 14 weeks (approximately four months), prompting discussions about feasibility and resource allocation.

Development Challenges

• Concerns arise regarding whether existing resources can expedite processes; technical details need further exploration by experienced team members familiar with Odoo.

Group Dynamics and Planning

Team Collaboration Insights

• Emphasis on deliverables suggests potential limitations in direct progress due to technical complexities; collaboration among team members is essential for effective planning.

Class Participation and Next Steps

Engagement Strategies

• Encouragement for students to actively participate in class discussions while acknowledging contributions from various group members enhances collaborative learning experiences.

Closing Remarks

Future Class Expectations

• In upcoming classes, focus will shift towards comprehensive project management planning, including timelines and methodologies. Students are encouraged to prepare accordingly.