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

Introduction and Class Engagement

Opening Remarks

• The instructor greets the class, encouraging enthusiasm and energy for the session.

• Acknowledges students as they join, creating a welcoming atmosphere for participation.

• Asks students about their understanding of previous topics related to project management and predictive planning.

Project Management Overview

• Introduces the concept of knowledge areas in project management, emphasizing quality, risk, finance, and resources.

• Highlights the importance of distinguishing between project formulation and project management.

Planning in Project Management

Importance of Planning

• Stresses that planning is crucial across all aspects: scope, requirements, quality, risks, resources, and finances.

• Discusses common pitfalls where technical experts overlook essential elements like expectations and environment during planning.

Challenges Faced

• Identifies issues arising from miscommunication with stakeholders who may lack technical knowledge.

• Describes how these challenges can lead to cost overruns or time delays due to inadequate validation processes.

Tools for Effective Project Management

Essential Tools

• Mentions tools such as Work Breakdown Structure (WBS), requirement traceability matrix, and network diagrams as critical for effective project execution.

• Explains how network diagrams help visualize task sequences and identify critical paths within projects.

Financial Considerations

• Emphasizes the need to accurately assess costs against budget constraints while managing resources effectively.

Execution Phase Insights

Launching Projects

• Discusses the significance of thorough planning before launching projects to ensure successful execution.

Continuous Evaluation

• Encourages ongoing assessment during execution to adapt plans based on real-time feedback from team performance.

Assessments and Evaluations

Upcoming Evaluations

• Informs students about an upcoming evaluation related to module two content that requires timely completion.

Importance of Knowledge Retention

• Reminds students that active engagement with material is necessary for long-term retention of knowledge gained throughout the course.

Student Participation

Encouraging Interaction

• Invites students who have not yet introduced themselves or wish to share insights about their experiences in class discussions.

Personal Experiences Shared by Students

Balancing Studies with Family Life

• A student shares her experience balancing studies with family responsibilities while supporting her spouse's education journey.

Learning Through Collaboration

• The student discusses how she has learned about technology through conversations with her husband regarding his studies in electronic engineering.

Project Documentation Insights

Updating Project Documents

• Discussion on updating project documentation based on evolving phases rather than maintaining a single comprehensive document.

Strategic Alignment

• Emphasizes aligning individual projects with broader strategic goals within an organization’s IT framework.

Importance of Measuring Progress in Agile Sprints

Sprint Duration and Results

• The speaker emphasizes the need to measure progress during sprints, noting that a month-long sprint may not yield results if requirements are not met or attention is lacking.

• Suggestion to implement three-month cycles instead of one-month sprints to allow for multiple deliverables and better tracking of progress.

• Understanding different communication styles is crucial; some stakeholders require detailed explanations while others prefer concise updates.

Return on Investment (ROI)

• Discussion on ROI highlights the importance of demonstrating tangible benefits from new systems, such as reduced incidents and improved stability compared to previous solutions.

• A significant reduction in generated incidents was noted, showcasing the effectiveness of the new system over two months.

System Availability and Integration Benefits

High Availability Features

• The new system allows access from any device globally, enhancing operational flexibility for various roles.

• Faster point-of-sale transactions were achieved with the new system compared to its predecessor.

Lessons Learned from Implementation

• A survey on user satisfaction is proposed as a lesson learned from managing this project, emphasizing agile methodologies over predictive approaches.

Communicating Value through Numbers

Evidence-Based Communication

• Stakeholders respond better to quantifiable data; presenting financial losses avoided due to fewer incidents resonates more than qualitative descriptions alone.

Introduction to Agile Methodologies

Understanding Agile Framework

• The speaker clarifies that project management itself isn't a methodology but encompasses various methodologies including agile practices.

Assessing Class Knowledge on Agile Methodologies

Engagement Through Interaction

• An interactive approach is used by asking participants about their familiarity with agile methodologies, fostering engagement and gauging knowledge levels.

Defining Agility in Project Management

Concept of Agility

• Agility refers more to adaptability rather than speed; it’s essential for responding effectively within changing environments in technology projects.

Tools and Techniques in Agile Practices

Popular Agile Tools

• Various tools like Lean, Design Thinking, Extreme Programming, and Scrum are mentioned as part of agile practices that facilitate team collaboration and iterative learning.

Learning Through Experience

Continuous Improvement

• Emphasizes that expertise comes through repeated practice and learning from mistakes over time—similar principles apply in software development.

Adapting to Rapid Changes in Technology

Need for Adaptability

• The rapid evolution of technology necessitates an agile approach; constant changes require teams to be flexible and responsive rather than rigidly following outdated plans.

Embracing Failure as Part of Growth

Learning from Mistakes

• Highlighting Thomas Edison’s perspective on failure illustrates that making mistakes is integral to achieving success—agile methodologies embrace this concept by allowing quick iterations.

Continuous Evolution in Solutions

Innovation Cycle

• Organizations must continuously evolve their products or services based on technological advancements; staying competitive requires ongoing adaptation.

Technology's Role Across Industries

Universal Application

• All sectors—including banking, education, finance—are increasingly reliant on technology for decision-making processes which drive profitability.

Challenges with Bureaucratic Structures

Limitations of Traditional Approaches

• Some industries face bureaucratic hurdles that hinder agility; government entities often struggle with implementing rapid changes due to regulatory constraints.

Agile Contracts and Project Management

Understanding Agile vs. Predictive Contracts

• The distinction between agile contracts, which are based on evolution, and predictive contracts, which focus on results, is emphasized as crucial for project management.

• Budgeting issues are discussed; while budgets may not be problematic, time estimations often lead to challenges in project execution.

• A subscription model for an e-commerce platform is introduced, highlighting different plans: free, entrepreneur, and business.

Strategic Product Management

• The conversation shifts towards the importance of commercial management strategies over mere technological solutions in product offerings.

• Emphasis is placed on prioritizing people over processes within agile frameworks to enhance collaboration among stakeholders.

Principles of Agile Methodology

Key Agile Principles

• The twelve principles of agile methodology are presented as foundational guidelines for satisfying customer needs and embracing change.

• Frequent delivery of functional products is highlighted as essential; each sprint should yield a working product increment.

Team Collaboration

• Daily collaboration between business stakeholders and developers is necessary for successful agile projects; high-performance teams are vital.

• Managing stress from frequent changes in tools or technologies (e.g., Angular vs. Python) requires strong leadership skills to keep teams motivated.

Motivation and Communication in Teams

Understanding Team Dynamics

• Effective motivation involves understanding individual team members' personal goals rather than just providing general encouragement.

• Face-to-face communication is stressed as critical for gauging team morale and ensuring clarity in discussions about project progress.

Importance of Visibility

• Keeping cameras on during virtual meetings enhances non-verbal communication cues that can indicate team members' true feelings about their work environment.

Measuring Product Functionality

User-Centric Measurement

• It's important to measure product functionality based on real user feedback rather than solely relying on developer assertions about performance.

Sustainable Work Rhythm

• Maintaining a sustainable work rhythm prevents burnout; teams should operate at a pace they can sustain over long periods without excessive pressure.

Addressing Team Challenges

Scrum Master Role

• Regular meetings led by the Scrum Master help identify obstacles faced by the team, allowing for timely interventions to maintain productivity.

Recognizing Contributions

• Acknowledging individual contributions through small rewards or recognition helps maintain morale and encourages continued effort from team members.

Culture of Agility in Organizations

Organizational Culture Impact

• The discussion highlights how organizational culture significantly influences agility; a culture resistant to change hinders effective implementation of agile practices.

Continuous Improvement

• Continuous attention to technical excellence ensures that teams remain competitive by adapting quickly to new technologies or methodologies.

Business Agility

Adapting Business Practices

• Companies must assess their ability to adapt quickly to market changes; those with rigid structures struggle with agility compared to more flexible organizations.

Future Workforce Considerations

• As AI technology evolves, traditional roles may diminish; businesses need agility not only in operations but also in workforce development strategies.

This structured summary captures key insights from the transcript while adhering strictly to your formatting requirements.

Understanding Company Culture

The Nature of Culture in Organizations

• Culture is defined as the attitude of individuals within a company, impacting overall harmony and collaboration.

• A lack of accountability leads to blame-shifting among employees, undermining teamwork despite claims of familial culture.

• Companies with poor organizational culture struggle to implement technological changes effectively.

Principles for Agile Transformation

• Key principles for adopting agility include transparency, productivity improvement, and continuous learning.

• Creating a happy work environment and applying design thinking are essential for fostering innovation.

Embracing Agility in Technology

Defining Agility

• Agility involves iterative development and learning from experiences, akin to creating a minimum viable product (MVP).

• Solutions should be customer-focused rather than technology-driven; understanding user needs is crucial.

Tools and Methodologies

• Extreme programming criteria and high-performance team management are vital components of agile practices.

• SCRUM is highlighted as the most widely used agile framework, emphasizing teamwork and collective effort.

The Iterative Process in Agile Development

Learning Through Iteration

• Iterative processes allow teams to learn from each cycle, improving efficiency over time through practice.

• Teams often experience significant reductions in task completion times through repeated iterations.

SCRUM as an Agile Framework

• There is debate on whether SCRUM qualifies as a methodology due to its focus on uncertainty and adaptability.

Core Principles of Agility

Transparency, Adaptability, Inspection

• Transparency ensures open communication within teams; knowledge sharing enhances collaboration.

• Adaptability allows teams to pivot quickly based on changing requirements or feedback from stakeholders.

Benefits of Agile Practices

Continuous Improvement

• Regular inspections lead to ongoing improvements in processes and outputs; feedback loops are integral to success.

Client Collaboration

• Close collaboration between clients and teams fosters motivation and aligns project goals with client expectations.

Roles Within the SCRUM Framework

Key Positions Defined

• The roles include Scrum Master, Product Owner, and Team Members who collaborate during sprints for effective delivery.

Sprint Planning Process

• Sprint planning involves prioritizing tasks based on client requests while considering team capacity for execution.

Managing Change in Agile Projects

Handling Complexity

• Teams must adapt when faced with unforeseen complexities during project execution; flexibility is key.

Retrospective Meetings

• Retrospectives allow teams to reflect on their performance after each sprint, identifying areas for improvement.

Understanding the Sprint Backlog and Team Commitment

The Role of the Sprint Backlog

• The sprint backlog consists of tasks that the team has committed to complete within a specified timeframe, emphasizing agility in task management.

• If the workload is too high, additional teams can be brought in based on budget availability to ensure all tasks are addressed.

Task Allocation and Execution

• On day one of the sprint, team members select their respective tasks (e.g., Juan takes task one), initiating collaborative work towards completion.

• The Scrum Master acts as a facilitator rather than a traditional project manager, addressing team issues and ensuring smooth progress.

The Role of the Scrum Master

Responsibilities and Support

• The Scrum Master resolves technical issues (e.g., computer problems), modifies requirements when necessary, and provides personal support to team members facing challenges.

• They also engage with team members personally to maintain motivation and interest in their work.

Daily Stand-ups

• Daily stand-up meetings last about 15 minutes where the Scrum Master checks on progress, identifies obstacles, and offers assistance as needed.

Sprint Completion and Review Process

End of Sprint Deliverables

• At the end of each sprint cycle (typically two to four weeks), deliverables are reviewed by stakeholders or users for feedback on quality and necessary changes.

Handling Feedback

• Positive feedback is welcomed; however, constructive criticism leads to adjustments being made before finalizing any product features.

Retrospective Meetings

Team Reflection

• After user reviews, teams hold retrospective meetings to discuss improvements such as format preferences for presentations or inter-departmental coordination issues.

Addressing Challenges

• Issues like traffic affecting attendance are discussed; suggestions include adjusting meeting times or formats for better participation.

Agile vs. Traditional Project Management

Flexibility in Work Hours

• Agile methodologies prioritize achieving goals over strict adherence to schedules; flexibility allows teams to meet objectives without rigid time constraints.

Distinction Between Roles

• Differences between project managers (focused on predictive methods with set timelines/budgets) versus Scrum Masters (who facilitate agile processes without needing deep technical expertise).

Hybrid Project Management Approaches

Combining Methodologies

• In hybrid projects, both roles may coexist; project managers handle financial aspects while Scrum Masters focus on facilitating agile practices within teams.

Complexity Considerations

• Projects' complexity determines whether an agile or predictive approach is more suitable; e-commerce projects often require agility due to dynamic requirements.

Clarifying Roles: Delivery Manager vs. Scrum Master

Functionality Comparison

• While both roles may share similar profiles, they have distinct responsibilities—Scrum Masters focus on team dynamics while delivery managers ensure timely production releases.

Navigating Hybrid Environments

Managing Dual Responsibilities

• In hybrid settings, professionals must balance traditional project management duties with agile facilitation skills depending on project needs.

Evolving Expertise

• As practitioners gain experience managing various types of projects (predictive/agile/hybrid), their skill sets expand significantly enhancing career prospects.

Upcoming Class Focus

Future Learning Objectives

• Next classes will delve into specific roles within agile frameworks including events and artifacts essential for effective implementation.