Technology for Product Managers

Explore how a technology team operates, cultivate empathy for developers, and learn to plan with engineering while gaining insight into web app development and git and GitHub.

Recognize programming as an art fueled by creativity and the 'click' moment that sparks solutions. Balance focus, planning, and context switching to align engineering work with unpredictable software development.

Track and analyze issues from board tools like Jira or Trello, identify blockers, and rewrite code, ensuring tests and pull requests move features toward production.

This lesson warns against one person per project, promotes knowledge dissemination through team collaboration, triads to reduce context switching, and prioritizes delivering customer-focused features via focused efforts.

Create a productive environment between product and technology teams by boosting communication, alignment, and synergy. Learn practical tips to empower developers and deliver higher quality work while keeping everyone happier.

Break the stereotype of the unapproachable developer by championing clear, assertive communication between product and tech; align on priorities, estimations, and a learning culture, including pair programming.

As a product manager, unite business and engineering through clear agreements, trust, and stakeholder alignment, and cultivate a tech supporter within the team for collaboration.

Negotiate scope and deadlines to preserve quality, avoid a snowball of technical debts, and protect your team, staying pragmatic while guiding product direction.

Explore technical debt, including active versus passive debt and strategic MVP trade-offs, and learn to measure quality, address bugs, testing, and documentation to protect user experience and release velocity.

Prioritize and estimate effectively by applying the Pareto principle and various prioritization methods, and explore the complexity of systems and teams that shape these decisions.

Prioritize as the product manager to align product goals amid uncertainty, balancing time, money, and engineering demands. Establish a contract with stakeholders to align scope and manage estimates versus predictions.

Discover the Pareto principle and apply the 80/20 rule to prioritization and estimations, focusing on the 20% of features that deliver 80% of value and defining the MVP.

Discover practical prioritization methods you can use today, including Moscow, impact versus effort, the bug method, and Eisenhower, to rank initiatives by value, effort, and urgency.

Prioritize and estimate with awareness of complex, adaptive software systems. Emphasize self-organizing teams, feedback, and fail-fast learning to deliver value amid uncertainty.

Explore the practicality of estimates in software delivery, advocating small, frequent increments, trust, and continuous delivery while considering methods like historical data, Monte Carlo, and planning poker.

Explore fundamental tech terms and concepts, including cloud, arm, microservice monoliths, legacy systems, DevOps, and cache strategies with sync and async communication.

Explore how the cloud uses geographic and local replicas to provide scalable computing power, availability, fault tolerance, and services like SaaS, PaaS, IaaS, and FaaS.

Break a monolithic server into small, specialized microservices with their own databases, accessible through an API gateway. This approach enables independent teams, language diversity, and resilient, scalable architectures.

Understand monolith architecture, with a single server housing the UI, business logic, and data access. Weigh its easy deployment and testing against the single point of failure and scalability limits.

Understand how legacy systems differ from monoliths, why neglecting technical debt and documentation harms user experience, and the need for a quality culture and careful migration strategies.

Embrace DevOps as a culture spanning planning, coding, building, testing, deployment, and production operations, with engineers owning the end-to-end flow and automations that accelerate delivery while reducing costs.

frameworks act as toolboxes and exoskeletons with conventions to build web and mobile apps, while libs are small, open-source black-box code for specific tasks like RG or CPF validation.

Cache stores temporary data in memory to speed access and reduce io calls, enabling offline use by serving data from memory. Manage invalidation when data changes to keep cache accurate.

Explore the differences between sync and async communication in web APIs, including request–response, message queues, web hooks, fire-forget patterns, and how async enables scalable processing.

Celebrate the journey through technology for product managers by sharing this course with colleagues, leaving a review, and providing feedback for more content.