Please enable JavaScript.
Coggle requires JavaScript to display documents.
Software Product Life Cycle, Full name: Nicolás Armando Alba Murillo -…
Software Product
Life Cycle
Development
Use Agile framework here
Lean UX
Scrum
Kanban
Daily Meetings
Dev Team talk about
What he did
What he will do tomorrow
What issues he had
Scrum Master leads this meeting
Team should understand the rituals
Why it is valuable for the team
Know the status of the team
The objective is sync the team
PM negotiate the better rituals
for the team
User Stories
PO priorizate them
The team creates the US
specially the PO
The dev team helps PO about technical things
The dev team estimates the USs
Fibonnaci
PO approves the creation of the US
Grooming sessions
Planing sessions
The sprint goal is defined by the selected US's
The dev team select the most valuable US that could be finish in the sprint
PM could use the US taken to do some flow diagrams
PM measure some metrics about the process in the spring
Burn down
Velocity
Capacity
Refirement sessions
Types
Technical Debts
Bugs
Features
Enhacements
Product Owner leads where we have to go
It's like the captain of a pirate boat
If he drives well the ship
He knows the direction of the path
Product Manager monitors the process
Identify risks
Identify blocks
Mitigation plans
It helps with the visiliby of the project
for Stakeholders and clients
To get help/resources if needed
ideation
Understand which is the problem of the user and client
Product Manager and Product Designer are very important here
Interview user
Understand the person
He doesn't know what he wants
Anatomy of an Interview
Build trust with him
Don't influence him
Know how he feels (The climax)
Reflection
Conclusion
Confirm what you found
in the interview
Don't talk about solution
Talk about problem
Creates a validated prototype
Wireframes
Mockups
Technical devs
help here about
texts
Fast drawings
Functionality Testing
It validates how easy it is for the user
Don't wait to be perfect, the time is gold
QA could help here
Use iterations until you have a valuable ideation
User - Person
Release
Release to users to make available
It depends of the kind of the proyect
Start up
Make sure the requirements are satisfied
Review initial documentation/configuration
Review infrastructure
Create process of how to release
Scale up
The team has experience because they did it before
PM motorize the previous written process
If PM has many projects, he should prioritize what project is first
Operation
Customer Success is very important here
What happen if there are problems if bussiness logic
Some unexpected bug in a feature
Marketing should create a good plan
PM monitorizes this process
Make sure marketing is on the same page
The increment of the product is released
Maybe users don't understand some feature
it's very strange, but could happen
Maybe it's depends on the culture
Design
Maybe you will regulate something
For instance
The healthcare
See the laws if applicable
Lawyers could help here
PM Talk with Tecnical Team
See if it possible
How easy/hard is the implementation
Maybe the scope could be change
Negotiations
Dev Team do technical diagrams
PM Talk with Design Team
PM See the budget
Profits and loses document
Justify the investment
The salary
The cost of the product
The tech infrastructure
Since the development, it's the most expensive phase this helps with minimize the costs
Analytics
PM analize the results and metrics
See the betters features
The information presented should be easy to understand for everybody
It helps to all the team to improve
it should be written as visual
PM do this
We learned if the product worked
or not worked
Also, we could learn what we have to do to works better the product
Full name:
Nicolás Armando Alba Murillo