Discover and read the best of Twitter Threads about #Scrum
Most recents (24)
A recent devBetter . com discussion:
"How can we automate moving stories from current to next sprint in Azure DevOps?"
You're trying to automate away pain that is a symptom of a problem with your process.
#AzureDevOps #DevOps #scrum
"How can we automate moving stories from current to next sprint in Azure DevOps?"
You're trying to automate away pain that is a symptom of a problem with your process.
#AzureDevOps #DevOps #scrum
The underlying problem is that you're trying to stuff too much into a sprint. If you're close to accurate, then you should be over half the time and under half the time, and only by a little bit, so there shouldn't be enough work to require automation.
If you have enough work that you need to automate it, then probably you're over more than half the time and by more than a story or two.
If that's the case, the solution isn't automation, it's putting fewer things in your sprint.
If that's the case, the solution isn't automation, it's putting fewer things in your sprint.
Vamos con un hilo interesante de puntos esenciales de #ProjectManagement, que podemos aplicar a cualquier proyecto que estemos llevando a cabo, independientemente de su tamaño o tipo. Muy importante si estamos trabajando con revisiones bajo modalidad de #AgileAudit.
[1] #ProjectManagement CICLO DE VIDA DEL PROYECTO. ¿Tienes definidas las etapas o fases que cubrirá el proyecto? Por ejemplo autorización, diseño, construcción y entrega. Si no son fases, puedes considerar la emisión de entregables al alcanzar ciertos hitos del proyecto.
[2] #ProjectManagement ALCANCE GEOGRÁFICO. ¿Describes en qué lugares o zonas se desarrollará el proyecto? Tener claras las ubicaciones geográficas te dará la oportunidad de establecer las personas contacto en dichas ubicaciones, y determinar el alcance real del trabajo.
Let’s talk about the software developed by #Ukrainian engineers to assist UA against #Russian aggression (Delta, MilChat, etc)
I have been researching this topic, their development cycles, and use in combat; and I want to share with you some findings.
Large🧵(1/20)
I have been researching this topic, their development cycles, and use in combat; and I want to share with you some findings.
Large🧵(1/20)
I would like to make it clear that this reflection comes from #OSINT, and that this thread will not compromise #Ukrainian #OPSEC
There could be interpretation errors (most sources were in Ukrainian, a language I do not speak), so corrections are welcome
(2/20)
There could be interpretation errors (most sources were in Ukrainian, a language I do not speak), so corrections are welcome
(2/20)
First, it should be noted that none of these tools could be considered a #Wunderwaffe
They will undoubtedly help #Ukraine in its war effort, but having them will not win the war. This software will be an element to be taken into account in combination with others factors
(3/20)
They will undoubtedly help #Ukraine in its war effort, but having them will not win the war. This software will be an element to be taken into account in combination with others factors
(3/20)
Reasons NOT to use #MobProgramming as a software development strategy:
1. Mob programming may only be suitable for some types of projects, teams, or initiatives. It may be more effective for certain tasks or projects but less effective for others.
1. Mob programming may only be suitable for some types of projects, teams, or initiatives. It may be more effective for certain tasks or projects but less effective for others.
2. Mob programming may not be suitable in a distributed work world because it requires a high level of collaboration and communication. To communicate effectively, geographically dispersed teams may need a significant investment in tools and infrastructure.
3. The infrastructure required for #mobprogramming may be more complex or costly than traditional software development methods.
Listening to podcasts can transform your PM career.
Problem: There are more than 850,000 of them.
Solution: Top 11 PM podcasts you'd be crazy to miss: 🧵
#productmanagement #prodmgmt
Problem: There are more than 850,000 of them.
Solution: Top 11 PM podcasts you'd be crazy to miss: 🧵
#productmanagement #prodmgmt
1. Lenny's Podcast @lennysan
Probably the best product podcast on this planet.
The true king of podcasts.
More: lennyspodcast.com
You can't miss an episode with @cagan:
lennyspodcast.com/the-nature-of-…
Probably the best product podcast on this planet.
The true king of podcasts.
More: lennyspodcast.com
You can't miss an episode with @cagan:
lennyspodcast.com/the-nature-of-…
2. This Is Product Management by @feedbackloopcom
This is a must-listen for anyone involved in creating, designing, selling, and managing products or services.
Apple: podcasts.apple.com/us/podcast/thi…
Spotify: open.spotify.com/show/5qoM5evv8…
This is a must-listen for anyone involved in creating, designing, selling, and managing products or services.
Apple: podcasts.apple.com/us/podcast/thi…
Spotify: open.spotify.com/show/5qoM5evv8…
Are you using Lean Startup, Agile, or Product Discovery?
Be careful. If you cherry-pick, you can spectacularly fail.
Why is this the case? And how to avoid it?🧵
#productmanagement #prodmgmt #agile #scrum
Be careful. If you cherry-pick, you can spectacularly fail.
Why is this the case? And how to avoid it?🧵
#productmanagement #prodmgmt #agile #scrum
1. Lean Startup
Take the MVP test results as proof and execute your plan in a waterfall style. Without regular inspection and adaptation, your plan will fall apart like a house of cards.
Shot to the moon.
Take the MVP test results as proof and execute your plan in a waterfall style. Without regular inspection and adaptation, your plan will fall apart like a house of cards.
Shot to the moon.
2. Agile
Pick an Agile framework like Scrum. Start without validating your business model. Came up with ideas and deliver them in iterations.
Most ideas are not going to work. And your product probably never had a chance to achieve the Product-Market fit.
Gambling and waste.
Pick an Agile framework like Scrum. Start without validating your business model. Came up with ideas and deliver them in iterations.
Most ideas are not going to work. And your product probably never had a chance to achieve the Product-Market fit.
Gambling and waste.
The biggest collection of PM learning resources: books, podcasts, videos, internships, free courses, conferences, frameworks, and much more (October 2022): 🧵
#productmanagement
#productmanagement
Am I getting too radical?
The 5 non-negotiable truths about product management: 🧵
#productmanagement #agile #scrum
The 5 non-negotiable truths about product management: 🧵
#productmanagement #agile #scrum
1. Creating products is complex. It can't be planned in detail.
When working on products, you must run small experiments, inspect, and adapt as you go.
"In complex environments, what will happen is unknown." - Scrum Guide 2020
When working on products, you must run small experiments, inspect, and adapt as you go.
"In complex environments, what will happen is unknown." - Scrum Guide 2020
2. Most of your ideas are just not going to work.
- The customers do not desire it
- Users won't know how to use it
- Ideas are not viable for your business
- Technology doesn't allow it
"The first truth is that at least half of your ideas are just not going to work" - @cagan
- The customers do not desire it
- Users won't know how to use it
- Ideas are not viable for your business
- Technology doesn't allow it
"The first truth is that at least half of your ideas are just not going to work" - @cagan
In #Agile, the daily scrum (aka daily standup), is a #scrum ceremony that occurs once each day of the sprint.
The daily scrum is a time-boxed event (15 mins) in which the team syncs & plans its activities for the day. #agilecoach #productmanagement
blog.logrocket.com/product-manage…
1/14
The daily scrum is a time-boxed event (15 mins) in which the team syncs & plans its activities for the day. #agilecoach #productmanagement
blog.logrocket.com/product-manage…
1/14
The purpose of the daily standup is to inspect the progress being made toward the sprint goal and to adapt the work where necessary.
This ensures that the team’s work and progress is visible to all team members and provides a regular feedback loop for the team.
2/14
This ensures that the team’s work and progress is visible to all team members and provides a regular feedback loop for the team.
2/14
Effective daily scrums promote collaboration and self-organization.
For PMs, this is a game changer: rather than having to liaise, track, and manage work across the team, the daily standup encourages team members to self-organize and hold each other accountable.
3/14
For PMs, this is a game changer: rather than having to liaise, track, and manage work across the team, the daily standup encourages team members to self-organize and hold each other accountable.
3/14
If you’re part of a cross-functional product team, you may have taken part in a sprint retrospective. If you’re new to #productmanagement, this guide will get you up to speed on what a sprint retro is and why it’s important
#agile #agilecoach #scrum blog.logrocket.com/product-manage…
1/12
#agile #agilecoach #scrum blog.logrocket.com/product-manage…
1/12
A sprint retrospective is a scrum ceremony that is held once a sprint has ended to reflect on the work that has just taken place.
The team reviews processes, ways of working, and key learnings with the aim of improving the team’s performance during subsequent sprints.
2/12
The team reviews processes, ways of working, and key learnings with the aim of improving the team’s performance during subsequent sprints.
2/12
A sprint retrospective is held at the end of a sprint, before the next sprint begins. If your sprint is 2 weeks long, the sprint retro meeting might be as short as 1 hour. If you’re working on a longer sprint cycle or on a larger team, the retro might last up to 3 hours.
3/12
3/12
Here is my unpopular perspective on story points. Story points are just a number. Don’t get me wrong though, it’s a good information to know for the team so that they can predict their velocity and commit to deliverables. #agile #scrum #developer #storypoints
The use of story points has always been a huge topic for debate. Some say it is useful for agile software development teams, others say it is of no use for business. Both of them are correct.
But here is where I have a strong opinion, as someone who has worked in many software development teams, both as a software developer and an engineering manager in the last two decades of my career. Story points are a bad measure for a software developer’s performance.
1/14
𝐓𝐡𝐢𝐬 𝐢𝐬 𝐛𝐢𝐥𝐢𝐧𝐠𝐮𝐚𝐥 𝐜𝐨𝐧𝐭𝐞𝐧𝐭 𝐄𝐍 & 𝐅𝐑
Today is Star Wars day and let's discover what à Scrum Master is!
Aujourd'hui, c'est la journée Star Wars, découvrons ensemble qui est le Scrum Master
@Uncle3john @AgnideOket
#Scrum #ScrumMaster #StarWarsDay #agile
𝐓𝐡𝐢𝐬 𝐢𝐬 𝐛𝐢𝐥𝐢𝐧𝐠𝐮𝐚𝐥 𝐜𝐨𝐧𝐭𝐞𝐧𝐭 𝐄𝐍 & 𝐅𝐑
Today is Star Wars day and let's discover what à Scrum Master is!
Aujourd'hui, c'est la journée Star Wars, découvrons ensemble qui est le Scrum Master
@Uncle3john @AgnideOket
#Scrum #ScrumMaster #StarWarsDay #agile
SCRUM Master this, Scrum Master that.
Wtf is this!!!
SCRUM Master ci, Scrum Master ça. C'est quoi encore 🤣🤣🤣
Wtf is this!!!
SCRUM Master ci, Scrum Master ça. C'est quoi encore 🤣🤣🤣
Yes I am, à Scrum Master
1/16
Ohayo Mina San.
Je suis de retour avec une astuce simple pour préparer sa semaine de manière agile en 12 étapes.
Je vous fais découvrir cela avec l'élève plus cool et le plus studieux du mangaverse: Sakamoto de: Sakamoto desu ga?
#agile #ScrumMaster
@AgnideOket @Uncle3john
Ohayo Mina San.
Je suis de retour avec une astuce simple pour préparer sa semaine de manière agile en 12 étapes.
Je vous fais découvrir cela avec l'élève plus cool et le plus studieux du mangaverse: Sakamoto de: Sakamoto desu ga?
#agile #ScrumMaster
@AgnideOket @Uncle3john
2/16
Si tu utilises @NotionHQ ou @clickup tu peux aussi appliquer l'astuce #notion #clickup #trello @trello
Si tu utilises @NotionHQ ou @clickup tu peux aussi appliquer l'astuce #notion #clickup #trello @trello
3/16
On part d'où on est et de ce qu'ont fait déjà puis on s'améliore 😉
On part d'où on est et de ce qu'ont fait déjà puis on s'améliore 😉
Hello
Comment allez-vous ?
Aujourd'hui, je partage avec vous un petit pan d'agilité avec un invité très agile
Alors qu'en pensez-vous ?
J'ai hâte d'avoir vos avis.
#agile #scrum #hinatashoyo #agilecoach
Thread 1/4
Comment allez-vous ?
Aujourd'hui, je partage avec vous un petit pan d'agilité avec un invité très agile
Alors qu'en pensez-vous ?
J'ai hâte d'avoir vos avis.
#agile #scrum #hinatashoyo #agilecoach
Thread 1/4
2/4
My Project Management journey!
I just stated the Google Project Management: Professional Certificate through Coursera and I have decided to update my learning journey, so this will be a thread of my progress. #BlackTechTwitter #womenintech #projectmanagement #baddiesintech
Day 1
Course: Foundations of Project Management
Now I have basic understanding of project management and what a project manager does (planning and organizing, managing tasks, budgeting and controlling costs).
Course: Foundations of Project Management
Now I have basic understanding of project management and what a project manager does (planning and organizing, managing tasks, budgeting and controlling costs).
I know, it is kind of "dangerous" to tap the SAFe framework :) Not, that many people would care anymore. Or a lot of customers would care. But SAFe is primarily a training business - and usually criticizing SAFe results in being bashed by SAFe trainers.
To be honest, I also don't care about SAFe anymore. 7 years ago, after looking in any of its details, it was clear to me, this is not a skillful way. Having looked into it in 2021, my point of view was strongly confirmed.
A major problem with SAFe though is, how critique is assumed to be "bashing". Why? Not at all because SAFe is so great. But because it triggers emotions of trainers and consultants, who make a great living of something, that I interpret as uneducated intervention.
Conf n°3 : pilotage par la valeur : le chemin plutôt que les outils - REX par Timothée Chevrier
#agilegrenoble #agile #scrum @AgileGrenoble
#agilegrenoble #agile #scrum @AgileGrenoble
La valeur métier est relative, elle sert à prioriser, elle est à peu près stable dans le temps (contrairement à la priorité). Le modèle de Kano aide à définir la valeur métier. #agilegrenoble
Qui utilise un indicateur de valeur métier actuellement ? --> on est moins de 10 à lever la main sur environ 80 personnes [en tant qu'ergonome ça fait mal... mais peut-être que l'action de mesure de cette valeur par des ux /po n'est pas partagée dans les équipes ?]
#agilegrenoble
#agilegrenoble
Conf n°2 : Product Owner pour les nuls
Product Owner : responsable de produit si on traduit. Sa mission : maximiser la valeur produite dans le temps imparti. C'est aussi le représentation des parties prenantes. #agilegrenoble21 @AgileGrenoble
Product Owner : responsable de produit si on traduit. Sa mission : maximiser la valeur produite dans le temps imparti. C'est aussi le représentation des parties prenantes. #agilegrenoble21 @AgileGrenoble
Ses compétences :
1 - connaissance du métier, des enjeux, des risques, de la reglementation
2 - possède la vision du produit, il y croit, il fait ce qu'il faut pour y arriver, c'est notre "guide"
#agilegrenoble21 #agilegrenoble #agile #scrum
1 - connaissance du métier, des enjeux, des risques, de la reglementation
2 - possède la vision du produit, il y croit, il fait ce qu'il faut pour y arriver, c'est notre "guide"
#agilegrenoble21 #agilegrenoble #agile #scrum
3 - sait dire non : à son équipe, à ses responsables, supérieurs, commerciaux...
4 - faire preuve d'ouverture d'esprit, être à l'écoute des retours, des équipe pour revoir ses certitudes
5 - a l'esprit de synthèse pour convaincre ses interlocuteurs et faire comprendre ses choix
4 - faire preuve d'ouverture d'esprit, être à l'écoute des retours, des équipe pour revoir ses certitudes
5 - a l'esprit de synthèse pour convaincre ses interlocuteurs et faire comprendre ses choix
#NoEstimates, un mouvement hétérogène et controversé lancé en 2012 sur Twitter 🔮
Le sujet vu par @ddreptate dans un meetup organisé par @ByondSM 🧶
Le sujet vu par @ddreptate dans un meetup organisé par @ByondSM 🧶
—On est mauvais à estimer (+ c’est gros — on est précis)
—Processus fastidieux
—Détourne de la création de valeur (focus coût vs. valeur)
—Celle-ci vient de l’implication des personnes et de la capacité à apprendre rapidement dans un monde VUCA (rien de mécanique ou identique)
—Processus fastidieux
—Détourne de la création de valeur (focus coût vs. valeur)
—Celle-ci vient de l’implication des personnes et de la capacité à apprendre rapidement dans un monde VUCA (rien de mécanique ou identique)
BIAIS COGNITIFS, une des raisons principales pour mal estimer
—Biais d’ancrage: on va tjrs rester figés sur une 1ere info, on sera influencés par ça
—Biais de confirmation: on donne + d’importance aux infos qui vont venir confirmer nos croyances
—...
#neuroscience #NoEstimates
—Biais d’ancrage: on va tjrs rester figés sur une 1ere info, on sera influencés par ça
—Biais de confirmation: on donne + d’importance aux infos qui vont venir confirmer nos croyances
—...
#neuroscience #NoEstimates
Hey, parlons un peu d'agilité 🙌
je vous propose une série de #Thread sur l'#Agilité et la "méthode" agile #Scrum.
Je vais essayer de partager l'essentiel de la philosophie derrière ces concepts et comment ça se propage dans l'entreprise.
Here we GO 😎
je vous propose une série de #Thread sur l'#Agilité et la "méthode" agile #Scrum.
Je vais essayer de partager l'essentiel de la philosophie derrière ces concepts et comment ça se propage dans l'entreprise.
Here we GO 😎
[THREAD n°1] Historique, Génèse
Avant d'aller trés loin dans les méthodes et autres, parlons d'abord de la génèse.
L'agilité est entrain de se généraliser de plus en plus dans les entreprises. Elle a d'abord démarré dans les services informatiques. Plus particulièrement dans
Avant d'aller trés loin dans les méthodes et autres, parlons d'abord de la génèse.
L'agilité est entrain de se généraliser de plus en plus dans les entreprises. Elle a d'abord démarré dans les services informatiques. Plus particulièrement dans
la gestion de projets logiciels. En effet, les projets informatiques étaient gérés suivant un cycle de développement logique séquentielle appelé cycle en cascade ou #waterfall. ces modes de gestion sont hérités des industries manufacturières
Tu seras #Agile mon kid
Je ne veux voir aucune larme glisser sur cette gueule héroïque
Et ce #Scrum tout sculpté pour atteindre des sommets fantastiques
Que seul une rêverie pourrait surpasser
... 😇
Je ne veux voir aucune larme glisser sur cette gueule héroïque
Et ce #Scrum tout sculpté pour atteindre des sommets fantastiques
Que seul une rêverie pourrait surpasser
... 😇
Tu seras #Agile mon kid
Je ne veux voir aucune once #prédictive
Ni des airs, ni des gestes qui veulent dire
Et dieu sait, si ce sont tout de même les pires à venir
Te castrer pour quelques #analyses
... (ça passe 😋)
Je ne veux voir aucune once #prédictive
Ni des airs, ni des gestes qui veulent dire
Et dieu sait, si ce sont tout de même les pires à venir
Te castrer pour quelques #analyses
... (ça passe 😋)
Tu seras #Agile mon kid
Loin de toi ces finesses tactiques
Tous ces plans d'origine qui rigidifient vos guises
Sous prétexte d'être le messie fidèle de ce cher modèle anarchique
Loin de toi ces finesses tactiques
Tous ces plans d'origine qui rigidifient vos guises
Sous prétexte d'être le messie fidèle de ce cher modèle anarchique
تابعت النقاش حول منهجية ال #Agile اللي بدأها الدكتور مازن @mznmel وخلوني ألخص وجهة نظري.
١- الضعف التقني (الشديد أحيانًا) لدى الكثير من فرق البرمجة في السعودية والقفز السريع للادارة هربًا من البرمجة مشكلة كبيرة. شخصيا غير مقتنع بمدير منتج برمجي ما اشتغل برمجة ٥-١٠ سنوات.
١- الضعف التقني (الشديد أحيانًا) لدى الكثير من فرق البرمجة في السعودية والقفز السريع للادارة هربًا من البرمجة مشكلة كبيرة. شخصيا غير مقتنع بمدير منتج برمجي ما اشتغل برمجة ٥-١٠ سنوات.
ما أعرف صراحة كيف شخص يبي يصير مدير منتج برمجي او يصير scrum master وهو لم يعمل قبل كمبرمج. أحد متطلبات التوظيف ك product manager في قوقل مثلا هي ان تكون software engineer بخبرة طويلة.
I have stopped providing Wireframes to my clients. This has a shift in the focus and expectations of clients from a #UX Principal Consultant. Now they take a keen interest in Ecosystem Diagrams, Lumascapes, Unmoderated Observational Study, User Journey, improving Operations
before suggesting products to achieve an objective, Macro Economy Behaviour, Individual's Personality, Socio-Political and Demographic Constraints. I learned this by following mature ecosystems like the transaction between Doctor Consultants and Testing Labs.
Similarly, the transaction between Lawyer Consultants and Para Legal Team. So, now I pass all the documentation to the UI designer and achieve the design iteratively, progressing over Kanban or Scrum Agile Framework. Anyway, these days Design Systems have made it easy to follow
One Day Design Sprint. Morning 8 am Start. Just one USP User Flow. Virtual Projection everything on Apple Watch size screen. Limited Space, limited IA, limited ID & linear task flow. 2 PM Usability Testing. 4 PM improvisation on data collected. 6 PM wrapup. @AJSmartDesign
I was following Design Sprint of @AJSmartDesign that is 4 days long. Then it strike me that does Screen Size (apple watch, phone, tablet, Desktop, TV, Projector) proportional to the Design Sprint's duration (week)?
A 4 day sprint will have multiple objective. A 1 day sprint will have USP objective cutting out all the noise. A 1 day sprint means failing at the end of the day if the USP can't be discovered or usability testing don't get the expected output. Much better than failing on the
