[[Software Product Management Specialization]] # Introduction to Software Product Management by University of Alberta Part of the [Software Product Management Specialization](https://www.coursera.org/specializations/product-management) ## Project Success, Why Agile? - I already attended the [[Agile Project Management - Coursera]] - Timing is the most important factor that determine business success - Goal of the team is to meet expectation of client, meeting their needs. - Be adaptable. Learn from mistakes makes it better. ## Agile Manifesto - A product manager is not a messenger between stakeholders, but facilitate communication directly. - Implement the values that do work.. don't have to use all at this time. ## Delivering Working Software - Focus on delivering software that work, prototype. - This satisfy the customer. - What is the feature that customer most valued. - More frequent delivery, more change to improve. - Working software is primary measure of progress. - Feature is complete only when written, tested and documented. - How to be change friendly ## Flexible Design - How to be change friendly. - Change is good. - Sustainable pace is important. - Simplicity - Deliver what is the most essential. high impact delivery ## Collaborative Communication - Principle 9 - trust that motivated team will figure things out to get to the goal. - =="The important thing is not your process. The important thing is your process for improving your process" - Henrik Kniberg (Agile Trainer)== - That is very true. #Reflection #Reflexivity - Self-organising team. Self assign tasks when complete task. ## Why Process? - Process organises the work and people into phase to get the work done. ## Why Requirements? - Need to be specific, requests, and features. ## Why Planning? NO AD HOC development - =="Planning is bringing the future into the present so that you can do something about it now. - Alan Lakein" - For Time and Cost estimates, Risk management. Resource planning - Time estimate is decided by the team and product manager. only developer know how long it will take. - Risk management - "What if...", then risk management plan. ## Why Monitoring? - Throughout the project, it is important for product manager to supervise the process. - Monitor - Progress tracking - Velocity - Whats wrong, whats going right. - Visibility (Everyone know what is going on) - Transparency - so everyone know, and bring team together.