<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>points on batmat.net</title>
		<link>https://batmat.net/tags/points/</link>
		<description>Recent content in points on batmat.net</description>
		<generator>Hugo</generator>
		<language>fr-FR</language>
		
		
		
		
			<lastBuildDate>Sun, 15 Sep 2019 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://batmat.net/tags/points/index.xml" rel="self" type="application/rss+xml" />
			<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>
	</channel>
</rss>
