In any project, there are parameters for measuring success:
completion of project within budget
delivery of complete features or requirements
In software product management, it is the same. However, there are added items:
The number of post-release bugs
The technical support needed after a software release
The software product’s customer rating
The revenue generated
The client’s satisfaction
It is basically a lot, huh? Well, a software product manager will help identify the product and project success by checking the above parameters for and make sure that the development efforts are directed towards the delivery of a quality product.
Agile Software Development
Agile, from the definition of Miriam-Webster dictionary, is having a quick resourceful and adaptable character. So when we say agile software development, it is the set of software development principles created for effective and adaptive software development where it prioritizes 4 core values:
Individuals and interactions
Response to change
Below are the 12 Agile principles from the www.agilemanifesto.org, with infographics designed by the University of Alberta for the Coursera Course: Introduction to Software Product Management:
Pardon me if I am now using my blog as my online notes, but I am now on a learning journey! I have realized a lot this 2020, in terms of career, lovelife (that’s for another blog post ;-)) and finances. Now, I am taking one step at a time to improve myself, and the series of blogs I am writing are records of my learning journey. So if you are okay with learning more about my world, feel free to read and follow. 🙂
To start, what is software product management? Well, for one, software product management is different from project management. Though there are common features for both; however, the difference lies on the application. Project management is a broad field that can be applied in any development scenario (like preparing for a wedding, building a house, etc) whereas software product management describes practices for project management but particularly aimed for creating software products.
To achieve a better software, just like in learning, you must have a goal to accomplish. In software product management, there are three goals, particular for each member of the team:
Client – the goal of the client is to make sure that the software product meets their needs and solves their problem. If a client is happy with the product, the software is validated.
Developer – the goal of the developer is to make sure that the software they are developing are done right — meaning the design and the implementation frontend and backend satisfies the needs of the client. Here, the developers conducts reviews and tests to make sure the software is verified.
Product Manager – the goal of the product manager is to manage the development process of the software and organize the work of everyone involved. Here, the project manager makes sure there is clear communication, clear objectives and clear feedback so both the developers and the clients are happy.
In short, the goals in software product management are: clients ensures they have the right product, the developers verifies they have done the right product, and the product manager confirms that the requirements and process for both are managed right.
So, the role of the software product manager is important in any software development (which is basically what I do for a new project). A software product manager is in charge of the success of a software product. This role involves understanding the product from the client’s point of view and requires effective communication and motivation of the development team members.
So, am I ready to start learning and taking the Software Product Management Specialization, a Coursera course offered by University of Alberta? Well, yeah, that’s for sure!!
Please bear with me as I post more and more blogs on my learning journey, but if you are also interested in this field, feel free to read and follow. 🙂