<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Agile on batmat.net</title>
		<link>https://batmat.net/tags/agile/</link>
		<description>Recent content in Agile on batmat.net</description>
		<generator>Hugo</generator>
		<language>fr-FR</language>
		
		
		
		
			<lastBuildDate>Sun, 22 Sep 2019 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://batmat.net/tags/agile/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Challenge Your Team, With Deep Care</title>
				<link>https://batmat.net/2019/09/22/challenge-your-team-with-deep-care/</link>
				<pubDate>Sun, 22 Sep 2019 00:00:00 +0000</pubDate>
				<guid>https://batmat.net/2019/09/22/challenge-your-team-with-deep-care/</guid>
				
				<description> Over the last years, I have come to read and reflect more and more on some aspects of great teamwork. There is now quite a corpus of litterature discussing what makes high performing teams.&#xA;Feeling safe When I tweeted a few days ago:&#xA;took me literally years to discover and understand why sane conflict in a team is not only good, but even required.&#xA;Care and Challenge.&#xA;Getting to know a bit more what you don’t know is progress right?&#xA;</description>
			</item>
			<item>
				<title>On Story Points</title>
				<link>https://batmat.net/2019/09/15/on-story-points/</link>
				<pubDate>Sun, 15 Sep 2019 00:00:00 +0000</pubDate>
				<guid>https://batmat.net/2019/09/15/on-story-points/</guid>
				
				<description> I see many people complaining about the crappy tool that story points are. I agree, this tool is very imperfect. We still however consciously make the choice to use them in our team, so why?&#xA;Clarifying scope as a team Basically, using story points estimation is the less worst tool that we have handy as a way to trigger discussions as a team.&#xA;We require Acceptance Criteria, and try to refine them until we have estimations that are closer with each other during the planning poker.&#xA;</description>
			</item>
			<item>
				<title>Why Managers Should Not Give Their Technical Opinion</title>
				<link>https://batmat.net/2016/04/19/why-managers-should-not-give-their-technical-opinion/</link>
				<pubDate>Tue, 19 Apr 2016 00:00:00 +0000</pubDate>
				<guid>https://batmat.net/2016/04/19/why-managers-should-not-give-their-technical-opinion/</guid>
				
				<description> A Good Manager Should Never Voice A Technical Opinion. Wait, what? Why exclude them if they could be useful? Management is too often badly considered. In my opinion, it’s because we actually rarely encounter good managers. You know, useful, inclusive, psychologist, able to catalyze work, and never get in the way, you have known plenty of them right?&#xA;Being a good manager is hard.&#xA;Like being a good developer.&#xA;It takes passion, time, experience, reading, and so many other things. And by trying to chase too many rabbits, you’re taking the risk to never even catch one.&#xA;</description>
			</item>
	</channel>
</rss>
