Remove the feeds module
This commit is contained in:
parent
acfd1cca8d
commit
0c98be96eb
851 changed files with 840 additions and 10348 deletions
|
@ -87,14 +87,5 @@
|
|||
"processed": "\n <p>I was reading a Twitter thread recently that <a href=\"https:\/\/twitter.com\/allenholub\/status\/1594786089994067969\">started with this tweet<\/a>.<\/p>\n\n<p>TL;DR:<\/p>\n\n<blockquote>\n <p>\"Measuring output (e.g. velocity) is a waste of time. It's outcomes you care about - customer happiness.\"<\/p>\n<\/blockquote>\n\n<p>This is definitely something that I agree with.<\/p>\n\n<p>I can't remember the last time I looked at an output burndown chart or a velocity score.<\/p>\n\n<p>I'd rather focus on what outcomes have been delivered and adding value to clients and customers.<\/p>\n\n<p>What features did we release, what bugs did we fix, and what impact and value did that provide?<\/p>\n\n<p>What increased revenue or improved a customer's experience?<\/p>\n\n<p>I may have a sprint or cycle where I only deliver one or two large tasks, but those are major features that have been requested, a bug affecting a user's experience, or a task that unblocks future tasks.<\/p>\n\n<p>In that situation, my velocity may not be good and could be improved by working on multiple smaller tasks, but which outcomes provide the most value?<\/p>\n\n ",
|
||||
"summary": null
|
||||
}
|
||||
],
|
||||
"feeds_item": [
|
||||
{
|
||||
"imported": "1970-01-01T00:32:50+00:00",
|
||||
"guid": null,
|
||||
"hash": "ead1c8b01bd5cd04cfb3c0a1d516473b",
|
||||
"target_type": "feeds_feed",
|
||||
"target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
|
||||
}
|
||||
]
|
||||
}
|
Loading…
Add table
Add a link
Reference in a new issue