#scrum — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #scrum, aggregated by home.social.
-
Okay this might be a really weird question but I have one question regarding command-line-only workflows.
I am already used to and very comfortable working in the command line as is.
And as any heavy user of the terminal will know, at some point you'll probably start writing scripts and functions and aliases to create your own little shortcuts for common tasks or preferred program call-up options and such. So do I.
Now my weird little 'problem' is that I don't always remember all of the scripts, aliases, functions and even programs I built for my workflow over the years off the top of my head.
For example, I might have an "update" alias set up, but nine out of ten times will still enter the command manually out of sheer habit.
Or I will have a calendar or to-do application for the CLI/TUI, but sometimes forget that I have it installed when I need it. Or I'll forget where the files are I set up to organise my journal or my time tracking.
Or going even further, I don't always remember all the neat features of my shell I could use, or the computing/typing habits I wanted to build, or the projects I have going on, and so on!
In a graphical desktop environment or on a mobile UI, you have tools like desktop shortcuts, quickstart icons or application launcher menus for an overview of all of your environment's user-facing programs. Seeing an icon out of the corner of my eye sometimes reminds me of things that a purely reactive user interface like a shell doesn't.
Now there's obviously ways to solve this that come to mind:
- writing a script that prints comprehensive documentation on everything, so I only need to remember that one script name.
- keeping a physical cheat sheet next to my computer.
- using a terminal multiplexer to have a permanent digital 'cheat sheet' or 'launcher' open at the side of the screen.
- trying to just automate these things by using cronjobs/services and shell init scripts to, for example, show me the weather and my to-do list automatically on boot so i don't have to remember these commands at all
- trying to keep a super organised self-documenting file system and harmonious custom dotfile configs so every config is in the same place, every program uses the same keybinds, all scripts are in
~/.bin/or something etc. - writing my own "home page" type greeter.
… but with all of these solutions, while they may work perfectly fine, something doesn't feel "right"!
I mean it's nice and good to print these things upon shell start, but later on in the day that won't be there to look at anymore. The multiplexer one is cumbersome. The self documenting file system organisation sounds like a pain to maintain.
I feel like this is an issue that corporate folks probably should have solved by now, as documenting workflows for employee handovers and stuff is critical there too. Do they use wikis for that? What about all those newfangled workflows like #scrum and #agile and all, do they have anything to say about documentation?
Can anyone relate? How do you handle this?
#linux #unix #commandLine #terminal #cli #tui #tech #askfedi #technology #fish #zsh #bash #shell
-
Okay this might be a really weird question but I have one question regarding command-line-only workflows.
I am already used to and very comfortable working in the command line as is.
And as any heavy user of the terminal will know, at some point you'll probably start writing scripts and functions and aliases to create your own little shortcuts for common tasks or preferred program call-up options and such. So do I.
Now my weird little 'problem' is that I don't always remember all of the scripts, aliases, functions and even programs I built for my workflow over the years off the top of my head.
For example, I might have an "update" alias set up, but nine out of ten times will still enter the command manually out of sheer habit.
Or I will have a calendar or to-do application for the CLI/TUI, but sometimes forget that I have it installed when I need it. Or I'll forget where the files are I set up to organise my journal or my time tracking.
Or going even further, I don't always remember all the neat features of my shell I could use, or the computing/typing habits I wanted to build, or the projects I have going on, and so on!
In a graphical desktop environment or on a mobile UI, you have tools like desktop shortcuts, quickstart icons or application launcher menus for an overview of all of your environment's user-facing programs. Seeing an icon out of the corner of my eye sometimes reminds me of things that a purely reactive user interface like a shell doesn't.
Now there's obviously ways to solve this that come to mind:
- writing a script that prints comprehensive documentation on everything, so I only need to remember that one script name.
- keeping a physical cheat sheet next to my computer.
- using a terminal multiplexer to have a permanent digital 'cheat sheet' or 'launcher' open at the side of the screen.
- trying to just automate these things by using cronjobs/services and shell init scripts to, for example, show me the weather and my to-do list automatically on boot so i don't have to remember these commands at all
- trying to keep a super organised self-documenting file system and harmonious custom dotfile configs so every config is in the same place, every program uses the same keybinds, all scripts are in
~/.bin/or something etc. - writing my own "home page" type greeter.
… but with all of these solutions, while they may work perfectly fine, something doesn't feel "right"!
I mean it's nice and good to print these things upon shell start, but later on in the day that won't be there to look at anymore. The multiplexer one is cumbersome. The self documenting file system organisation sounds like a pain to maintain.
I feel like this is an issue that corporate folks probably should have solved by now, as documenting workflows for employee handovers and stuff is critical there too. Do they use wikis for that? What about all those newfangled workflows like #scrum and #agile and all, do they have anything to say about documentation?
Can anyone relate? How do you handle this?
#linux #unix #commandLine #terminal #cli #tui #tech #askfedi #technology #fish #zsh #bash #shell
-
Okay this might be a really weird question but I have one question regarding command-line-only workflows.
I am already used to and very comfortable working in the command line as is.
And as any heavy user of the terminal will know, at some point you'll probably start writing scripts and functions and aliases to create your own little shortcuts for common tasks or preferred program call-up options and such. So do I.
Now my weird little 'problem' is that I don't always remember all of the scripts, aliases, functions and even programs I built for my workflow over the years off the top of my head.
For example, I might have an "update" alias set up, but nine out of ten times will still enter the command manually out of sheer habit.
Or I will have a calendar or to-do application for the CLI/TUI, but sometimes forget that I have it installed when I need it. Or I'll forget where the files are I set up to organise my journal or my time tracking.
Or going even further, I don't always remember all the neat features of my shell I could use, or the computing/typing habits I wanted to build, or the projects I have going on, and so on!
In a graphical desktop environment or on a mobile UI, you have tools like desktop shortcuts, quickstart icons or application launcher menus for an overview of all of your environment's user-facing programs. Seeing an icon out of the corner of my eye sometimes reminds me of things that a purely reactive user interface like a shell doesn't.
Now there's obviously ways to solve this that come to mind:
- writing a script that prints comprehensive documentation on everything, so I only need to remember that one script name.
- keeping a physical cheat sheet next to my computer.
- using a terminal multiplexer to have a permanent digital 'cheat sheet' or 'launcher' open at the side of the screen.
- trying to just automate these things by using cronjobs/services and shell init scripts to, for example, show me the weather and my to-do list automatically on boot so i don't have to remember these commands at all
- trying to keep a super organised self-documenting file system and harmonious custom dotfile configs so every config is in the same place, every program uses the same keybinds, all scripts are in
~/.bin/or something etc. - writing my own "home page" type greeter.
… but with all of these solutions, while they may work perfectly fine, something doesn't feel "right"!
I mean it's nice and good to print these things upon shell start, but later on in the day that won't be there to look at anymore. The multiplexer one is cumbersome. The self documenting file system organisation sounds like a pain to maintain.
I feel like this is an issue that corporate folks probably should have solved by now, as documenting workflows for employee handovers and stuff is critical there too. Do they use wikis for that? What about all those newfangled workflows like #scrum and #agile and all, do they have anything to say about documentation?
Can anyone relate? How do you handle this?
#linux #unix #commandLine #terminal #cli #tui #tech #askfedi #technology #fish #zsh #bash #shell
-
Okay this might be a really weird question but I have one question regarding command-line-only workflows.
I am already used to and very comfortable working in the command line as is.
And as any heavy user of the terminal will know, at some point you'll probably start writing scripts and functions and aliases to create your own little shortcuts for common tasks or preferred program call-up options and such. So do I.
Now my weird little 'problem' is that I don't always remember all of the scripts, aliases, functions and even programs I built for my workflow over the years off the top of my head.
For example, I might have an "update" alias set up, but nine out of ten times will still enter the command manually out of sheer habit.
Or I will have a calendar or to-do application for the CLI/TUI, but sometimes forget that I have it installed when I need it. Or I'll forget where the files are I set up to organise my journal or my time tracking.
Or going even further, I don't always remember all the neat features of my shell I could use, or the computing/typing habits I wanted to build, or the projects I have going on, and so on!
In a graphical desktop environment or on a mobile UI, you have tools like desktop shortcuts, quickstart icons or application launcher menus for an overview of all of your environment's user-facing programs. Seeing an icon out of the corner of my eye sometimes reminds me of things that a purely reactive user interface like a shell doesn't.
Now there's obviously ways to solve this that come to mind:
- writing a script that prints comprehensive documentation on everything, so I only need to remember that one script name.
- keeping a physical cheat sheet next to my computer.
- using a terminal multiplexer to have a permanent digital 'cheat sheet' or 'launcher' open at the side of the screen.
- trying to just automate these things by using cronjobs/services and shell init scripts to, for example, show me the weather and my to-do list automatically on boot so i don't have to remember these commands at all
- trying to keep a super organised self-documenting file system and harmonious custom dotfile configs so every config is in the same place, every program uses the same keybinds, all scripts are in
~/.bin/or something etc. - writing my own "home page" type greeter.
… but with all of these solutions, while they may work perfectly fine, something doesn't feel "right"!
I mean it's nice and good to print these things upon shell start, but later on in the day that won't be there to look at anymore. The multiplexer one is cumbersome. The self documenting file system organisation sounds like a pain to maintain.
I feel like this is an issue that corporate folks probably should have solved by now, as documenting workflows for employee handovers and stuff is critical there too. Do they use wikis for that? What about all those newfangled workflows like #scrum and #agile and all, do they have anything to say about documentation?
Can anyone relate? How do you handle this?
#linux #unix #commandLine #terminal #cli #tui #tech #askfedi #technology #fish #zsh #bash #shell
-
-
-
-
-
-
Scrum Master Day 2026: Neuer Präsenz-Workshop und mehr Zeit fürs Sparen
Der Frühbucherpreis für die Online-Konferenz Scrum Master Day 2026 gilt eine Woche länger und neu im Programm ist ein Vor-Ort-Workshop in Köln.
-
Scrum Master Day 2026: Neuer Präsenz-Workshop und mehr Zeit fürs Sparen
Der Frühbucherpreis für die Online-Konferenz Scrum Master Day 2026 gilt eine Woche länger und neu im Programm ist ein Vor-Ort-Workshop in Köln.
-
Scrum Master Day 2026: Neuer Präsenz-Workshop und mehr Zeit fürs Sparen
Der Frühbucherpreis für die Online-Konferenz Scrum Master Day 2026 gilt eine Woche länger und neu im Programm ist ein Vor-Ort-Workshop in Köln.
-
Scrum Master Day 2026: Neuer Präsenz-Workshop und mehr Zeit fürs Sparen
Der Frühbucherpreis für die Online-Konferenz Scrum Master Day 2026 gilt eine Woche länger und neu im Programm ist ein Vor-Ort-Workshop in Köln.
-
Scrum Master Day 2026: Neuer Präsenz-Workshop und mehr Zeit fürs Sparen
Der Frühbucherpreis für die Online-Konferenz Scrum Master Day 2026 gilt eine Woche länger und neu im Programm ist ein Vor-Ort-Workshop in Köln.
-
Как перестать имитировать Agile и начать получать результат
На Хабре немало статей о том, почему Agile не работает. И в большинстве из них авторы справедливо отмечают, что ритуалы превратились в формальности, Scrum выродился в бюрократию, команды имитируют активность. Всё так. Я хочу поговорить про другое - про глубинные причины неудач во внедрении Agile и конкретные способы наконец-то получить от методологии тот результат, который она способна дать. Предлагаю пошаговый алгоритм, построенный на принципах поведенческой психологии. Он работает не с ритуалами и артефактами, а с тем, что действительно движет изменениями, — с людьми, их привычками и поведением. Эта статья — не про то, что Agile плох. Она про то, как сделать его работающим.
https://habr.com/ru/companies/smartvalues/articles/1069860/
#изменения #scrum #change_management #поведение #agileтрансформация #поведенческая_психология #процессы #управление_проектами #agile
-
Как перестать имитировать Agile и начать получать результат
На Хабре немало статей о том, почему Agile не работает. И в большинстве из них авторы справедливо отмечают, что ритуалы превратились в формальности, Scrum выродился в бюрократию, команды имитируют активность. Всё так. Я хочу поговорить про другое - про глубинные причины неудач во внедрении Agile и конкретные способы наконец-то получить от методологии тот результат, который она способна дать. Предлагаю пошаговый алгоритм, построенный на принципах поведенческой психологии. Он работает не с ритуалами и артефактами, а с тем, что действительно движет изменениями, — с людьми, их привычками и поведением. Эта статья — не про то, что Agile плох. Она про то, как сделать его работающим.
https://habr.com/ru/companies/smartvalues/articles/1069860/
#изменения #scrum #change_management #поведение #agileтрансформация #поведенческая_психология #процессы #управление_проектами #agile
-
Как перестать имитировать Agile и начать получать результат
На Хабре немало статей о том, почему Agile не работает. И в большинстве из них авторы справедливо отмечают, что ритуалы превратились в формальности, Scrum выродился в бюрократию, команды имитируют активность. Всё так. Я хочу поговорить про другое - про глубинные причины неудач во внедрении Agile и конкретные способы наконец-то получить от методологии тот результат, который она способна дать. Предлагаю пошаговый алгоритм, построенный на принципах поведенческой психологии. Он работает не с ритуалами и артефактами, а с тем, что действительно движет изменениями, — с людьми, их привычками и поведением. Эта статья — не про то, что Agile плох. Она про то, как сделать его работающим.
https://habr.com/ru/companies/smartvalues/articles/1069860/
#изменения #scrum #change_management #поведение #agileтрансформация #поведенческая_психология #процессы #управление_проектами #agile
-
Was Bakterien 🦠 besser machen als dein #Scrum-Team - Richard Seidl
Bugs zu vermeiden ist die falsche Strategie. Was Bakterien und Motten über Trends, Hypothesen und Robustheit in Software-Projekten lehren.
https://www.richard-seidl.com/de/podcast/resiliente-softwareprojekte-natur/ #Projektmanagement #ProjectManagement -
Was Bakterien 🦠 besser machen als dein #Scrum-Team - Richard Seidl
Bugs zu vermeiden ist die falsche Strategie. Was Bakterien und Motten über Trends, Hypothesen und Robustheit in Software-Projekten lehren.
https://www.richard-seidl.com/de/podcast/resiliente-softwareprojekte-natur/ #Projektmanagement #ProjectManagement -
Was Bakterien 🦠 besser machen als dein #Scrum-Team - Richard Seidl
Bugs zu vermeiden ist die falsche Strategie. Was Bakterien und Motten über Trends, Hypothesen und Robustheit in Software-Projekten lehren.
https://www.richard-seidl.com/de/podcast/resiliente-softwareprojekte-natur/ #Projektmanagement #ProjectManagement -
Was Bakterien 🦠 besser machen als dein #Scrum-Team - Richard Seidl
Bugs zu vermeiden ist die falsche Strategie. Was Bakterien und Motten über Trends, Hypothesen und Robustheit in Software-Projekten lehren.
https://www.richard-seidl.com/de/podcast/resiliente-softwareprojekte-natur/ #Projektmanagement #ProjectManagement -
Почему Agile убивает стратегию, когда его масштабируют
Agile легко превращается в ловушку, когда спринты идут по плану, метрики растут, а стратегические задачи месяцами стоят на месте. Разбираемся, почему так происходит при масштабировании и где руководителю вернуть фокус на реальный результат.
https://habr.com/ru/companies/otus/articles/1068628/
#Agile #Scrum #масштабирование_Agile #стратегия #спринты #Velocity #Story_Points #управление_проектами #бизнесрезультат #стратегическое_управление
-
Почему Agile убивает стратегию, когда его масштабируют
Agile легко превращается в ловушку, когда спринты идут по плану, метрики растут, а стратегические задачи месяцами стоят на месте. Разбираемся, почему так происходит при масштабировании и где руководителю вернуть фокус на реальный результат.
https://habr.com/ru/companies/otus/articles/1068628/
#Agile #Scrum #масштабирование_Agile #стратегия #спринты #Velocity #Story_Points #управление_проектами #бизнесрезультат #стратегическое_управление
-
Почему Agile убивает стратегию, когда его масштабируют
Agile легко превращается в ловушку, когда спринты идут по плану, метрики растут, а стратегические задачи месяцами стоят на месте. Разбираемся, почему так происходит при масштабировании и где руководителю вернуть фокус на реальный результат.
https://habr.com/ru/companies/otus/articles/1068628/
#Agile #Scrum #масштабирование_Agile #стратегия #спринты #Velocity #Story_Points #управление_проектами #бизнесрезультат #стратегическое_управление
-
Hendrik Dahmke: Product Velocity braucht gemeinsames Verständnis
In diesem Gastbeitrag betrachtet Hendrik Dahmke Product Velocity aus der Perspektive eines Systems Engineers.
https://www.se-trends.de/hendrik-dahmke-product-velocity-braucht-gemeinsames-verstandnis/
#Menschen #ProductVelocity #Autonomie #Fhrung #Gastbeitrag #Management #Produktentwicklung #SAFe #Scrum #Systemdenken #Zusammenarbeit -
Hendrik Dahmke: Product Velocity braucht gemeinsames Verständnis
In diesem Gastbeitrag betrachtet Hendrik Dahmke Product Velocity aus der Perspektive eines Systems Engineers.
https://www.se-trends.de/hendrik-dahmke-product-velocity-braucht-gemeinsames-verstandnis/
#Menschen #ProductVelocity #Autonomie #Fhrung #Gastbeitrag #Management #Produktentwicklung #SAFe #Scrum #Systemdenken #Zusammenarbeit -
Hendrik Dahmke: Product Velocity braucht gemeinsames Verständnis
In diesem Gastbeitrag betrachtet Hendrik Dahmke Product Velocity aus der Perspektive eines Systems Engineers.
https://www.se-trends.de/hendrik-dahmke-product-velocity-braucht-gemeinsames-verstandnis/
#Menschen #ProductVelocity #Autonomie #Fhrung #Gastbeitrag #Management #Produktentwicklung #SAFe #Scrum #Systemdenken #Zusammenarbeit -
Software Testing: Was Bakterien besser machen als dein Scrum-Team
Die Softwareentwicklung kann sich von Strategien aus der Natur einiges abschauen, wie Anna Melbinger im Gespräch erläutert.
#AgileSoftwareentwicklung #IT #Journal #Projektmanagement #Scrum #Softwareentwicklung #Wirtschaft #news
-
Software Testing: Was Bakterien besser machen als dein Scrum-Team
Die Softwareentwicklung kann sich von Strategien aus der Natur einiges abschauen, wie Anna Melbinger im Gespräch erläutert.
#AgileSoftwareentwicklung #IT #Journal #Projektmanagement #Scrum #Softwareentwicklung #Wirtschaft #news
-
Software Testing: Was Bakterien besser machen als dein Scrum-Team
Die Softwareentwicklung kann sich von Strategien aus der Natur einiges abschauen, wie Anna Melbinger im Gespräch erläutert.
#AgileSoftwareentwicklung #IT #Journal #Projektmanagement #Scrum #Softwareentwicklung #Wirtschaft #news
-
Software Testing: Was Bakterien besser machen als dein Scrum-Team
Die Softwareentwicklung kann sich von Strategien aus der Natur einiges abschauen, wie Anna Melbinger im Gespräch erläutert.
#AgileSoftwareentwicklung #IT #Journal #Projektmanagement #Scrum #Softwareentwicklung #Wirtschaft #news
-
Software Testing: Was Bakterien besser machen als dein Scrum-Team
Die Softwareentwicklung kann sich von Strategien aus der Natur einiges abschauen, wie Anna Melbinger im Gespräch erläutert.
#AgileSoftwareentwicklung #IT #Journal #Projektmanagement #Scrum #Softwareentwicklung #Wirtschaft #news
-
🚧 A Developer mentions the same work four days running and still says "no blockers." Usually the team just doesn't share a definition of what an impediment is.
Working definition: anything that slows progress toward the Sprint Goal. Bad connection, interruptions, waiting on another team, broken builds, slow decisions, a poorly understood PBI. All impediments.
A trick: swap "impediment" for "slowdown," easier to admit. Then check the board for items stuck in one state for days.
An impediment you can't name is one nobody can remove.
https://agilepainrelief.com/glossary/impediments/?utm_source=mastodon&utm_campaign=archive-reshare
-
🚧 A Developer mentions the same work four days running and still says "no blockers." Usually the team just doesn't share a definition of what an impediment is.
Working definition: anything that slows progress toward the Sprint Goal. Bad connection, interruptions, waiting on another team, broken builds, slow decisions, a poorly understood PBI. All impediments.
A trick: swap "impediment" for "slowdown," easier to admit. Then check the board for items stuck in one state for days.
An impediment you can't name is one nobody can remove.
https://agilepainrelief.com/glossary/impediments/?utm_source=mastodon&utm_campaign=archive-reshare
-
🚧 A Developer mentions the same work four days running and still says "no blockers." Usually the team just doesn't share a definition of what an impediment is.
Working definition: anything that slows progress toward the Sprint Goal. Bad connection, interruptions, waiting on another team, broken builds, slow decisions, a poorly understood PBI. All impediments.
A trick: swap "impediment" for "slowdown," easier to admit. Then check the board for items stuck in one state for days.
An impediment you can't name is one nobody can remove.
https://agilepainrelief.com/glossary/impediments/?utm_source=mastodon&utm_campaign=archive-reshare
-
🚧 A Developer mentions the same work four days running and still says "no blockers." Usually the team just doesn't share a definition of what an impediment is.
Working definition: anything that slows progress toward the Sprint Goal. Bad connection, interruptions, waiting on another team, broken builds, slow decisions, a poorly understood PBI. All impediments.
A trick: swap "impediment" for "slowdown," easier to admit. Then check the board for items stuck in one state for days.
An impediment you can't name is one nobody can remove.
https://agilepainrelief.com/glossary/impediments/?utm_source=mastodon&utm_campaign=archive-reshare
-
🚧 A Developer mentions the same work four days running and still says "no blockers." Usually the team just doesn't share a definition of what an impediment is.
Working definition: anything that slows progress toward the Sprint Goal. Bad connection, interruptions, waiting on another team, broken builds, slow decisions, a poorly understood PBI. All impediments.
A trick: swap "impediment" for "slowdown," easier to admit. Then check the board for items stuck in one state for days.
An impediment you can't name is one nobody can remove.
https://agilepainrelief.com/glossary/impediments/?utm_source=mastodon&utm_campaign=archive-reshare
-
Fachbücher werden angefangen, nicht gelesen. Nach drei Wochen weißt du nicht mehr, wo du warst.
Seit dem Wochenende steht mein Buch komplett als Webseiten online. 34 Kapitel, jedes einzeln aufrufbar. Du hakst ab, was du gelesen hast. Die Suche geht über alle 43 Seiten. Und jeder Abschnitt hat einen Link zum Kopieren, wenn du einem Kollegen genau diese Stelle schicken willst.
Kostenlos. PDF und EPUB bleiben.
https://no-bullshit-agile.de/buch/?mtm_campaign=mastodon
#SoftwareEngineering #Programming #OpenSource #Scrum #Kanban
-
Fachbücher werden angefangen, nicht gelesen. Nach drei Wochen weißt du nicht mehr, wo du warst.
Seit dem Wochenende steht mein Buch komplett als Webseiten online. 34 Kapitel, jedes einzeln aufrufbar. Du hakst ab, was du gelesen hast. Die Suche geht über alle 43 Seiten. Und jeder Abschnitt hat einen Link zum Kopieren, wenn du einem Kollegen genau diese Stelle schicken willst.
Kostenlos. PDF und EPUB bleiben.
https://no-bullshit-agile.de/buch/?mtm_campaign=mastodon
#SoftwareEngineering #Programming #OpenSource #Scrum #Kanban
-
Fachbücher werden angefangen, nicht gelesen. Nach drei Wochen weißt du nicht mehr, wo du warst.
Seit dem Wochenende steht mein Buch komplett als Webseiten online. 34 Kapitel, jedes einzeln aufrufbar. Du hakst ab, was du gelesen hast. Die Suche geht über alle 43 Seiten. Und jeder Abschnitt hat einen Link zum Kopieren, wenn du einem Kollegen genau diese Stelle schicken willst.
Kostenlos. PDF und EPUB bleiben.
https://no-bullshit-agile.de/buch/?mtm_campaign=mastodon
#SoftwareEngineering #Programming #OpenSource #Scrum #Kanban
-
Fachbücher werden angefangen, nicht gelesen. Nach drei Wochen weißt du nicht mehr, wo du warst.
Seit dem Wochenende steht mein Buch komplett als Webseiten online. 34 Kapitel, jedes einzeln aufrufbar. Du hakst ab, was du gelesen hast. Die Suche geht über alle 43 Seiten. Und jeder Abschnitt hat einen Link zum Kopieren, wenn du einem Kollegen genau diese Stelle schicken willst.
Kostenlos. PDF und EPUB bleiben.
https://no-bullshit-agile.de/buch/?mtm_campaign=mastodon
#SoftwareEngineering #Programming #OpenSource #Scrum #Kanban
-
Fachbücher werden angefangen, nicht gelesen. Nach drei Wochen weißt du nicht mehr, wo du warst.
Seit dem Wochenende steht mein Buch komplett als Webseiten online. 34 Kapitel, jedes einzeln aufrufbar. Du hakst ab, was du gelesen hast. Die Suche geht über alle 43 Seiten. Und jeder Abschnitt hat einen Link zum Kopieren, wenn du einem Kollegen genau diese Stelle schicken willst.
Kostenlos. PDF und EPUB bleiben.
https://no-bullshit-agile.de/buch/?mtm_campaign=mastodon
#SoftwareEngineering #Programming #OpenSource #Scrum #Kanban
-
https://www.europesays.com/africa/370857/ Argentina 10-17 South Africa: Springboks survive Pumas fightback to edge Buenos Aires thriller #AllBlacks #Argentina #DigitalEdition #Final #NewZealand #rugby #Scrum #SouthAfrica #Springboks #stormers
-
„Ohne Schätzung kann ich dem Kunden nichts sagen.“ Der Einwand ist berechtigt. Die meisten NoEstimates-Debatten gehen genau daran vorbei.
Nur: Der Kunde will ein Datum. Story Points sind keins. Zwischen der 5 und dem Termin steht eine Velocity, die ihr aus den letzten Sprints hochrechnet. Die hält, solange sich nichts ändert. Sie ändert sich immer.
Warum ich die Punkte trotzdem für den falschen Streit halte:
https://no-bullshit-agile.de/das-ende-der-schaetzung-warum-story-points-ueberbewertet-sind.html?mtm_campaign=mastodon -
„Ohne Schätzung kann ich dem Kunden nichts sagen.“ Der Einwand ist berechtigt. Die meisten NoEstimates-Debatten gehen genau daran vorbei.
Nur: Der Kunde will ein Datum. Story Points sind keins. Zwischen der 5 und dem Termin steht eine Velocity, die ihr aus den letzten Sprints hochrechnet. Die hält, solange sich nichts ändert. Sie ändert sich immer.
Warum ich die Punkte trotzdem für den falschen Streit halte:
https://no-bullshit-agile.de/das-ende-der-schaetzung-warum-story-points-ueberbewertet-sind.html?mtm_campaign=mastodon -
„Ohne Schätzung kann ich dem Kunden nichts sagen.“ Der Einwand ist berechtigt. Die meisten NoEstimates-Debatten gehen genau daran vorbei.
Nur: Der Kunde will ein Datum. Story Points sind keins. Zwischen der 5 und dem Termin steht eine Velocity, die ihr aus den letzten Sprints hochrechnet. Die hält, solange sich nichts ändert. Sie ändert sich immer.
Warum ich die Punkte trotzdem für den falschen Streit halte:
https://no-bullshit-agile.de/das-ende-der-schaetzung-warum-story-points-ueberbewertet-sind.html?mtm_campaign=mastodon -
„Ohne Schätzung kann ich dem Kunden nichts sagen.“ Der Einwand ist berechtigt. Die meisten NoEstimates-Debatten gehen genau daran vorbei.
Nur: Der Kunde will ein Datum. Story Points sind keins. Zwischen der 5 und dem Termin steht eine Velocity, die ihr aus den letzten Sprints hochrechnet. Die hält, solange sich nichts ändert. Sie ändert sich immer.
Warum ich die Punkte trotzdem für den falschen Streit halte:
https://no-bullshit-agile.de/das-ende-der-schaetzung-warum-story-points-ueberbewertet-sind.html?mtm_campaign=mastodon
