Product, Projekt & Agile: Thoughts and articles that touch and cover Product and Project Management, for the majority with Agile Methodologies. These items include Market Observation, Competitive Analysis, Backlog Prioritisation, but also choice of tools and technology.
Running products in large organisations is a challenging task. Sebastian Lindemann of Product Coalition shares a few thoughts on high impact team cooperation modes.
How product teams can work together to maximize impact “Driving is easy if you are the only one the road“ … my driving instructor had many wise words to share. This one stuck with me as it is applies to so much more than driving a car.
Source: Doing the heavy lifting together
Marty Cagan of the Silicon Valley Product Group published an article only yesterday, comparing Product and Feature Teams. Apparently, the article generated so much feedback that Marty found it worthwhile clarifying a few of his thoughts and collect the gist of the feedback he received.
Every so often one of my articles seems to strike a chord, and this latest one on the difference between Product Teams and Feature Teams certainly seemed to do that. I am grateful for the very positive response. This morning I woke up to well over a hundred people that took the time to e-mail […]
It’s time for the last beta release of Python 3.8. Go find it at: https://www.python.org/downloads/release/python-380b4/ This release is the last of four planned beta release previews. Beta release previews are intended to give the wider community the opportunity to test new features and bug fixes and to prepare their projects to support the new feature release.
In an ideal world, product managers have plenty of data they can use to validate their idea before building the wrong product. Yana Yushkina describes her journey from a Data Analyst to a Product Manager.
She talks about characteristics a good PM should bring, that include foundational analytical understanding, curiosity not just for technology but to search for the right answers in data, a sense of responsibility and the ability to communicate.
All of that combined with the right metrics at hand and self sufficient mindset will give a Product Manager the right answer from data.
Via Product School.
GitHub today released a CI/CD Tool, GitHub Actions. With the tight integration into development workflows and rich, community maintained build-command, actions appears an interesting competitor in the market. As a minimum, the release indicates the importance of CI/CD for the modern software development lifecycle.
Developer productivity and frictionless workflows have been buzzwords for the past half decade and the arrival and rapid growth of Travis-CI, Jenkins or Cirlce-CI have proven the resonance in development organisations. GitHub has outstanding testimonials from day one on the announcement and the ecosystem appears to be ready to go.
It is an offering that comes with appealing integrations and a competitive price, that sure is worth watching.
GitHub Actions makes it easy to automate all your software workflows, now with world-class CI/CD. Build, test, and deploy your code right from GitHub. Make code reviews, branch management, and issue triaging work the way you want.
Should you be working in Product Management, this may well be a good selection for Sunday evening to watch:
As a product manager, you’ll want to continuously be seeking out new ways to learn, new information, fresh ideas, and inspiration. It’s a constant learning process, and it’s important to stay open and stay motivated. While there are many resources out there, including books, blogs, podcasts, influential people on social media, and tons of online publications, there is something we love about TED Talks.
Just a small observation I made during AWS Transformation Day. While the entire theme for the event was on transforming business, the schedule had one track for “Culture and Organizational Change” alone. While Culture and Organizational Change is a broad and huge topic, but it is necessary and makes the difference for agility in rapidly changing and competitive markets. Amazon has been talking about this for years and they share their knowledge with their partners.
On an attempt to find out how organizations actually master this, the perspective most consultants and companies I talked to during the event shared with me was rather sobering. Anyone exhibiting at that event merely offered to run any software project under an agile management. No support, consultancy or even efforts to drive actual change, whatsoever, at least nothing that would exceed a traditional software project scope.
Cultural and Organizational Change is something requiring executive buy in and is killed quickly by means of exhaustive efforts to plan ahead. Culture needs to embrace the possibility to change quickly, throughout the process. And the wish for management is human, to have transparency and perspective early in the process, it is just as natural in the process for developers to stay vague for items that are not yet clear.
Any cultural change needs to embrace bi-directual communication and the ability to break down complex. On first thought this sounds easy, but requires plenty of cooperation and trust in a clearly defined team. Culture is rooted in clear understanding of roles, responsibilities and not to mention last, trust of all members.
I cringe every time I see product teams use a spreadsheet to rank the ideas in their backlog based on some made-up math formula usually consisting of things like business value, user value, and technical difficulty. While this exercise is pervasive, it misses the point entirely. Our job is not to prioritize solutions. A product […]
Source: Prioritize Opportunities, Not Solutions | Product Talk
Source: 4 Keys to Empowering Your Product Team – Mind the Product
The organisation that I am part of introduced an overlaying Product Management department only fairly recently, less than a year ago. Early in the time it was exciting to see this role dedicated to market and customer perspective, but it raised questions over how this was different from Product Ownership from day one.
Over the course of the past year many discussions have been led and lot’s of articles have been led. This week Anthony Murphy shared his perspective and experiences on the Product Coalition. While my own experiences with this separated role have been predominantly positive, I tend to see the necessity to split responsibilities for larger organisations. The article is reflecting on why the Agile movement created the Product Owner in the way it did and how it was meant to abolish the Product Manager to start with.
Source: The Collision of Product Management and Product Ownership
Notifications