Inspiration och artiklar
Vi skriver regelbundet artiklar där vi delar med oss av vår kunskap och erfarenhet.
Anmäl dig till vårt nyhetsbrev
Några gånger per år samlar vi ihop vad som händer hos oss, erfarenheter från våra uppdrag och saker vi tycker är intressanta i vår omvärld. Resultatet blir ett nyhetsbrev fyllt med kunskap och tips som kan hjälpa dig och din organisation att växa.
Artiklar
Takeaways from Product at Heart in Hamburg
Another topic that was brought up by several speakers, including Bruce McCarthy, was the need for PM:s to understand the company they are operating in. Not all companies are digitally native, like a Spotify or Netflix, and may be more sales- or finance-driven. You need to understand this in order to help guide your team in the right direction and provide your stakeholders with the right insights and data
Lessons from a year in SAFe: If you talk about risks and dependencies long enough, eventually every team will have them
If we spend too much time on identifying dependencies and risks early on we’re probably never going to put anything into production. If you want to be as agile as possible, there is always a trade-off between the cost of knowing everything before we start development and finding it out as we go.
Lessons from a year in SAFe: Use the ART Planning Board to highlight the problems you’re trying to solve
The ART Planning Board in SAFe serves multiple purposes but one of the main things is to showcase the features we’re working on. It’s a setup that rewards attention to detail; clear descriptions, acceptance criteria and much more but at least from my experience, we rarely take the time to define which problem the feature is intended to solve, what data we have to prove that it’s actually a problem and how we will know if it has been solved.
Lessons from a year in SAFe: Don’t fixate on roles, look at teams’ maturity
Given that SAFe defines the PO and Scrum Master/Team Coach roles as critical, it’s easy to assume that they are always needed. I think that’s a misconception and instead I think you should take a look at each team’s maturity.
Why aren’t you delivering new functionality without telling everyone beforehand?
If a company doesn’t work with outcomes, it’s easy to think that the release of new functionality failed because a couple of users or employees complained about the lack of information or documentation beforehand.
Vem är Kristoffer?
Läs om hur Kristoffer hamnade på SeventyOne och hans värderingar och tankar på trender framåt.
Ask these 3 questions to improve Machine Learning Ethics
Ask these 3 questions to improve Machine Learning Ethics and be more mindful of biases and promote privacy & data protection throughout your ML lifecycle.
Vem är Nhan?
Läs om hur Nhan hamnade på SeventyOne och hennes värderingar och tankar på trender framåt.
