Müssen es immer die fetten Enterprise-Tools sein? @xahteiwi hat eine Diskussion über Nextcloud Deck für Kanban angestoßen. Das Fazit der Community: Es muss nicht immer Jira sein, aber ganz ohne Schmerzen geht's wohl nirgends (Performance-Probleme inklusive). Ein Tool macht noch keinen Prozess, aber ein schlechtes Tool tötet jeden Flow.

Zur Diskussion: https://mastodon.social/@xahteiwi/115635126527857964
Welches Tool nutzt ihr, um dem Jira-Monster zu entkommen?

4/4

#Kanban #Tools #Nextcloud #NoJira

"Cách quản lý phản hồi khách hàng không dùng Jira/Slack?כות từ cộng đồng SaaS: sử dụng Trello, Notion hoặc.Tasks. #feedback #management #SaaS #noJira #noSlack #dịchvuliênpéng #nghịchkhách"

https://www.reddit.com/r/SaaS/comments/1oaxutj/how_do_you_manage_client_feedback_loops_without/

What is your take on the concept of
- Discovery-"Stories"
- Delivery-"Stories"

Any opinion on it? What problem is solved here?

To me, that smells a bit waterfally. Is it just me?

#agile #story #userstory #productDevelopment #agileProductDevelopment #Scrum #jira #noJira #stories #waterfall #fakeAgile

Jira is like poison to some developers. Watched one that was doing brilliant while we were in #NoJira mode, and as soon as I had to inject Jira, wants to use Jira in silliest possible way to silo work over tracking goals.

We have been trained with fake / wrong kind of visibility that takes away from progress and productivity.

[Blog] A #NoJira health check. https://visible-quality.blogspot.com/2023/08/a-nojira-health-check.html

Describing the five ideas I failed to communicate when roles changed and team size doubled.

A NoJira Health Check

Ideas and experiences on software testing, software development, conference speaking and organizing.

So much for my #NoJira experiment: in a blitz of frustration, I poured the scope I held in my head to Jira tickets as I did not like the way the mismatch of my model and what was there. I hijacked "Other" issue type to track things I care to track - for now.
Queued up, not listened:

invidious.osi.kr/watch?v=IETVi…

www.youtube.com/watch?v=IETViz…
Maaret describes the culture at FSecure and the benefits her team discovered when they experimented with removing the Product Owner from their team (though there is still a Product Management group in the company). Her team found that the benefits included far greater productivity, solving problems they hadn’t managed to solve in years and becoming far more data-driven. Maaret describes the “superpower” have having a “feature team” that works across three different technical stacks, and how #NoProductOwner, #NoEstimates and #NoJira are working nicely.
Modern Agile Show #43 | Interview with Maaret Pyhäjärvi

Episode 43 of the Modern Agile Show features an interview with Maaret Pyhäjärvi (@maaretp), a Lead Quality Engineer at FSecure, an agile practitioner and the author of Strong Style Pair Programming, Mob Programming Guidebook and Exploratory Testing. Maaret describes the culture at FSecure and the benefits her team discovered when they experimented with removing the Product Owner from their team (though there is still a Product Management group in the company). Her team found that the benefits included far greater productivity, solving problems they hadn’t managed to solve in years and becoming far more data-driven. Maaret describes the “superpower” have having a “feature team” that works across three different technical stacks, and how #NoProductOwner, #NoEstimates and #NoJira are working nicely. She describes how her teams have shortened releases from every six months to every two weeks. Maaret’s team runs about 300,000 automated tests everyday on 14,000 virtual machines. Only a few of the FSecure developers use Test-Driven Development. The company also got rid of all Scrum Masters during a resizing. Coaching happens, yet it’s not an official title. Maaret is a fan of the Modern Agile principles and uses them in her work. You can learn more about Maaret and her work at https://maaretp.com/

Invidious