Relations between #daily stand-up meetings, work #satisfaction, and team #performance perceptions: the role of psychological safety
▻https://www.tandfonline.com/doi/full/10.1080/1359432X.2025.2508178?cookieSet=1
— Permalink
#management #standup #meeting #psychologicalsafety #efficacy #learning #agile
Les start-up, une hyper-innovation ? | France #culture
▻https://www.radiofrance.fr/franceculture/podcasts/la-suite-dans-les-idees/les-start-up-une-hyper-innovation-7030909
— Permalink
#startup #définition #entreprise #sociologie #économie #culture #innovation #financement #subvention #VC #investissement #risque #capitalsocial #capital #capitalisme #management #hiérarchie #horizontal #agile #organisation #travail #engagement #aidespubliques #idéologie #gouvernance #politique #administration #bureaucratie
#eigenfocus/eigenfocus: Self-Hosted - Project Management, Planning and Time Tracker
▻https://github.com/Eigenfocus/eigenfocus
— Permalink
Je ne compte plus les fois où j’ai entendu dire : « Nous, on est passés en #agile. » Pourtant, quand on creuse un peu, on découvre souvent une réalité bien différente. Derrière les post-it colorés, les #daily et les tableaux #Kanban flambant neufs, beaucoup de #projets ne sont pas agiles — ils jouent à l’être.
▻https://michelcampillo.com/blog/5243.html
Strengthening Large‐Scale #agile Teams: The Interplay of High‐Quality #relationships, Psychological Safety, and #learning From Failures
▻https://onlinelibrary.wiley.com/doi/10.1002/smr.2759
— Permalink
#leadership #dev #management #teamwork #psychologicalsafety #postmortem #trust #performance #productivity
Hiérarchie des estimations, malaise à l’échelle !
▻https://blog.octo.com/hierarchie-des-estimations-malaise-a-l%27echelle
— Permalink
#dev #management #agile #estimates
When a #team is too big - Alex Ewerlöf Notes
▻https://blog.alexewerlof.com/p/when-a-team-is-too-big
— Permalink
#management #agile #headcount #standup #complexity #communication #ownership #responsability #knowledge #mandate #generalist #specialist
#agile is Dead • Pragmatic Dave Thomas • GOTO 2015 - YouTube
— Permalink
#management #processes #softwaredevelopment #softwareengineering #consulting #methodology #ideology #hype #rant #PID #automation #rules #context #bestof
I Need #agile Methodology - YouTube
— Permalink
All Estimations Are Wrong, But None Are Useful
▻https://newsletter.techworld-with-milan.com/p/all-estimations-are-wrong-but-none
— Permalink
#estimates #forecast #planning #uncertainty #complexity #agile #softwareengineering #management
Unionize.fyi
▻https://unionize.fyi
— Permalink
#work #technology #dystopia #agile #burnout #union #ethics #management
Are You Using #ooda Loops in Your Software Project?
▻https://spin.atomicobject.com/ooda-loops-software-project
— Permalink
The Evolution of #agile Imposters
▻https://junglecoder.com/~saulrh/articles/evolution-of-agile-imposters.html
— Permalink
#softwareengineering #dev #management #estimate #bias #cognition
Le but ultime d’un #ERP est d’apporter la réactivité nécessaire afin que votre entreprise reste #agile au moins pour les 10 ans à venir ! Sinon je n’en vois guère l’intérêt.
▻http://consultant.lescigales.org/accompagner.html
#Youtrack est un outil de gestion de #projet qui peut être adapté aux processus de l’entreprise pour l’aider au suivi des projets et des tâches. Vous utilisez les tableaux de méthodologie #Agile, vous planifiez les sprints et les versions, vous maintenez une base de connaissances, travaillez avec des rapports et des tableaux de bord, créez des flux de travail qui suivent vos processus d’affaires ?
►https://michelcampillo.com/blog/6934.html
Agile as Trauma (▻https://doriantaylor.com/agile-as-trauma) | #agile...
▻https://diasp.eu/p/10425659
Agile as Trauma | #agile #management #trauma
#scrum et les mêlées quotidiennes
▻https://framablog.org/2019/11/08/scrum-et-les-melees-quotidiennes
Dans cet article, Matt, développeur à Los Angeles, s’attaque aux daily #standups, ces réunions de la méthodologie SCRUM, très à la mode actuellement. Sous ce terme se cache une réunion quotidienne d’au plus 15 minutes, se déroulant normalement debout, qui … Lire la suite
#Non_classé #Agile #Informatique #jira #Slack #trello
How Not To Kill Your Software Project
▻https://hackernoon.com/how-not-to-kill-your-software-project-a42b8ca1ae86?source=rss----3a8144e
Tons of software development projects tend to fail after launch for various reasons, of which the primary one is the lack of clear goals. Another almost equally significant but underestimated cause of failure is that a considerable number of these startups were solving the wrong problem.This situation is like a case of going a hundred miles per hour in the wrong direction and is quite common in the software development industry, but often binned under the ‘incompetence’ category (although, admittedly, that does play a role in some cases). It is an issue of poor communication between the parties involved.An ideal project would mean that all the organization’s staff at every level, as well as the target users, would be utterly convinced about the need to product and its ability to solve the (...)
#software-engineering #technology #startup #software-development #agile
Estimation — how can we estimate with confidence in software delivery?
▻https://hackernoon.com/estimation-how-can-we-estimate-with-confidence-in-software-delivery-20d8
Estimation — how can we estimate with confidence in software development?Introduction‘When will it be done?’ is one of the most common and difficult questions to answer in software development.Estimating in software is traditionally difficult, inaccurate most of the time, with project teams spending a significant amount of time on the process.There are a number of contributing factors to this. Part of it is that software development is a design activity, and thus hard to plan and estimate. Software is done with people, and it depends which individual people are involved. Individuals are hard to predict and quantify and humans in general are inherently bad at predictions [1]. Those teams that build the software are operating in an ever-changing business and technology landscape.The cost of (...)
#estimations #software-development #agile #hackernoon-top-story #noestimates
How to apply #agile manifesto in your software #development career
▻https://hackernoon.com/how-to-apply-agile-manifesto-in-your-software-development-career-9348884
If you work in the software development industry, I have no doubt that you’ve heard of Agile manifesto. Unlike the traditional way of…Continue reading on Hacker Noon »
The real cost of #transparency.
▻https://hackernoon.com/the-real-cost-of-transparency-866f865315?source=rss----3a8144eabfe3---4
When asked why he robbed banks, Willie Sutton famously responded, “Because that’s where the money is.” Similarly when creating a new product, we focused on enabling transparency, “Because that’s where the opportunity is.”At least, you’d think that’d be the case. Transparency as a concept appears to be widely accepted as a way for teams to be more effective. In fact if you look at the stated values of many newer companies, transparency is typically highlighted, as one of the 4 or 5 key attributes deemed critical to the success of the organization.Transparency just makes things . . . easier.However, we’re finding the day-to-day reality at most organizations is somewhat disconnected from their stated aspirations. I have been puzzled by why this should be the case. Why isn’t transparency more commonly (...)
#wip — Work in… What ? | #scrum.org
▻https://hackernoon.com/wip-work-in-what-scrum-org-e10c57e0a7a2?source=rss----3a8144eabfe3---4
WIP — Work in… What? | Scrum.orgBy: Peter Götz, Professional Scrum Trainer, Scrum.orgScrum and #kanban are a great combination. With this insight more and more Scrum Teams become aware of terms and phrases used in Kanban. Like ‘WIP’.When I have used this acronym in the past I have read it as ‘work in progress’. In his book ‘The Goal’ Eliyahu M. Goldratt consequently uses ‘work in process’. I realized this but didn’t give it much thought.This week, though, I discussed WIP with a colleague and we talked about the difference of ‘work in progress’ and ‘work in process’. And only then I realized that the two phrases mean something completely different.Work in Progressprogress (n): a forward or onward movement (as to an objective or to a goal)progress (v): 1. to move forward or 2. to develop to a higher, better, (...)
How Kickstarter’s Mark Wunsch Used Engineering #metrics to Make a Case for #refactoring
▻https://hackernoon.com/how-kickstarters-mark-wunsch-used-engineering-metrics-to-make-a-case-for
“Effective engineering leadership is being outcome-oriented,” says Kickstarter’s Mark Wunsch.When Mark first joined Kickstarter as VP of Engineering, one of his first decisions was to re-organize the engineering department, based on business-oriented objectives.Each 3–7 person scrum team focused on a different “essence,” or a different customer-facing part of the product. This helped engineering understand their work from a business perspective. Mark tells us, “The objective is not to ask, ‘Is the code good?’ but to ask ‘Is Kickstarter good?’”The engineers’ perspective, however, was difficult to communicate with leadership.The engineers were constantly bogged down by problems that were invisible to non-technical colleagues, such as legacy code. Kickstarter has been around for about 10 years, so a (...)
Technical Debt & #scrum: Who Is Responsible?
▻https://hackernoon.com/technical-debt-scrum-e26421953278?source=rss----3a8144eabfe3---4
Technical Debt & ScrumTL;DR: Technical Debt & ScrumIf technical debt is the plague of our industry, why isn’t the Scrum Guide addressing the question of who is responsibly dealing with it? To make things worse, if the Product Owner’s responsibility is to maximize the value customers derive from the Development Team’s work, and the Development Team’s responsibility is to deliver a product Increment (at least) at the end of the sprint adhering to the definition of “Done,” aren’t those two responsibilities possibly causing a conflict of interest?This post analyzes the situation by going back to first principles, as laid out in the Scrum Guide to answer a simple question: Who is responsible for keeping technical debt at bay in a Scrum Team?What Is Technical Debt?According to (...)
Improving your Definition of #done
▻https://hackernoon.com/improving-your-definition-of-done-d467c06837bf?source=rss----3a8144eabfe
By Simon Reindl, Professional #scrum Trainer, Scrum.orgThe purpose of Scrum is to create a potentially releasable Done product Increment, in order to realize business value. Many teams struggle in improving their Definition of Done. The technique described here allows for greater transparency on where the Definition of Done is, and what are the next steps.The intent is to provide a structure for the teams to reflect, and then build a plan on what to introduce to improve the quality of their product Increment. This could be run during a Sprint Retrospective, before starting a team, or at any time during a Sprint.Draw three nested triangles on a whiteboard or flip chart, as show in the image below. Label the centre rectangle “Now”, the middle rectangle “Next”, and the outer rectangle “Future”. (...)