diff --git a/A-B-Testing.md b/A-B-Testing.md new file mode 100644 index 0000000..7f1d54c --- /dev/null +++ b/A-B-Testing.md @@ -0,0 +1,7 @@ +## A/B Testing + +- [How A/B Testing at LinkedIn, Wealthfront and eBay Made Me a Better Manager](http://firstround.com/review/how-a-b-testing-at-linkedin-wealthfront-and-ebay-made-me-a-better-manager/) + +- [How Netflix does A/B Testing](https://uxdesign.cc/how-netflix-does-a-b-testing-87df9f9bf57c) - by Jessie Chen + +- [It’s All A/Bout Testing: The Netflix Experimentation Platform](https://medium.com/netflix-techblog/its-all-a-bout-testing-the-netflix-experimentation-platform-4e1ca458c15) - by Steve Urban, Rangarajan Sreenivasan and Vineet Kannan \ No newline at end of file diff --git a/Agile-Coach.md b/Agile-Coach.md new file mode 100644 index 0000000..2db225b --- /dev/null +++ b/Agile-Coach.md @@ -0,0 +1,7 @@ +## Agile Coach + +- [The Agile Coach Role at Spotify](http://joakimsunden.com/2013/04/the-agile-coach-role-at-spotify/) - by Joakim Sundén + +- [What is an Agile Coach?](https://www.linkedin.com/pulse/what-agile-coach-simon-powers) - by Simon Powers + +- [What Makes a Good Agile Coach?](https://www.linkedin.com/pulse/what-makes-good-agile-coach-pmi-acp-csp-agilepm-icp-acc-clsss) - by Tim Guay \ No newline at end of file diff --git a/Agile-Product-Roadmap.md b/Agile-Product-Roadmap.md new file mode 100644 index 0000000..45e8a45 --- /dev/null +++ b/Agile-Product-Roadmap.md @@ -0,0 +1,5 @@ +## Agile Product Roadmap + +- [10 Tips for Creating an Agile Product Roadmap](https://medium.com/@romanpichler/10-tips-for-creating-an-agile-product-roadmap-515637c8081b#.y413bsegz) - by Roman Pichler + +- [Agile Roadmapping: How To Think Big, Ship Fast And Always Keep Moving](https://blog.trello.com/agile-roadmapping-how-to-think-big-ship-fast) - by Janna Bastow \ No newline at end of file diff --git a/Antipatterns.md b/Antipatterns.md new file mode 100644 index 0000000..48bc3e0 --- /dev/null +++ b/Antipatterns.md @@ -0,0 +1,11 @@ +## Antipatterns + +- [10 Common Scrum Mistakes and How to Avoid Them](https://dzone.com/articles/10-common-scrum-mistakes-and-how-to-avoid-them) - by Dwight Kingdon + +- [16 Stand-up Anti-Patterns Threatening Your Transition to Scrum](https://age-of-product.com/stand-up-anti-patterns/) + +- [28 Product Backlog and Refinement Anti-Patterns](https://age-of-product.com/28-product-backlog-anti-patterns/) + +- [Dark Scrum](http://ronjeffries.com/articles/016-09ff/defense/) - by Ron Jeffries + +- [Zombie Scrum - Symptoms, Causes and Treatment](https://www.linkedin.com/pulse/zombie-scrum-symptoms-causes-treatment-barry-overeem) - by Barry Overeem \ No newline at end of file diff --git a/Backlog-Refinement.md b/Backlog-Refinement.md new file mode 100644 index 0000000..7f46813 --- /dev/null +++ b/Backlog-Refinement.md @@ -0,0 +1,3 @@ +## Backlog + +- [28 Product Backlog and Refinement Anti-Patterns](https://age-of-product.com/28-product-backlog-anti-patterns/) \ No newline at end of file diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md new file mode 100644 index 0000000..cb2ab4c --- /dev/null +++ b/CONTRIBUTING.md @@ -0,0 +1,46 @@ +## Contribution Guidelines + +Please note that this project is released with a [Contributor Code of Conduct](code-of-conduct.md). By participating in this project you agree to abide by its terms. + +The pull request should have a useful title. We are unlikely to accept pull requests with `Update readme.md` as the title. Please carefully read everything in `Adding to this list`. + +## Table of Contents + +- [Adding to this list](#adding-to-this-list) +- [Updating your Pull Request](#updating-your-pull-request) + +## Adding to this list + +Please ensure your pull request adheres to the following guidelines: + +- Look at previous suggestions before making a new one, as yours may be a duplicate. +- Make sure the entry is useful before submitting. That implies it has the author's name and a succinct description/"takeaway" after the link. + - **The entry format** should follow this model: `[The Title of Your Article](link) - by author. Takeaway: ...` + - Use a **-** to separate the link and description. +- Takeaways should avoid sub-bullets and be complete sentences. +- Use **quotation marks** when you're quoting verbatim. +- Make **one individual pull request per each new entry/suggestion**. +- Use [title-casing](http://titlecapitalization.com) (AP style), regardless of the style used by the original article. +- Add link additions in **alphabetical order**. + - Disregard articles (**the/an/a**) coming at the beginning of titles and use the next word. +- New categories or improvements to the existing categorization are welcome. +- Check your spelling and grammar. +- Make sure your text editor is set to remove trailing whitespace. + +Thank you for your suggestions! + +## Adding something to an awesome list: how-to + +If you have something awesome to contribute to this list, here's how you do it. + +You'll need a [GitHub account](https://github.com/join)! + +1. Visit this list's GitHub page. +2. Click on the `readme.md` file: ![Step 2 Click on Readme.md](https://cloud.githubusercontent.com/assets/170270/9402920/53a7e3ea-480c-11e5-9d81-aecf64be55eb.png) +3. Now click on the edit icon. ![Step 3 - Click on Edit](https://cloud.githubusercontent.com/assets/170270/9402927/6506af22-480c-11e5-8c18-7ea823530099.png) +4. Start editing the file text in the in-browser editor. Make sure you follow guidelines above. ![Step 4 - Edit the file](https://cloud.githubusercontent.com/assets/170270/9402932/7301c3a0-480c-11e5-81f5-7e343b71674f.png) +5. Say why you're proposing the changes, and then click on "Propose file change." ![Step 5 - Propose Changes](https://cloud.githubusercontent.com/assets/170270/9402937/7dd0652a-480c-11e5-9138-bd14244593d5.png) +6. Submit the [pull request](https://help.github.com/articles/using-pull-requests/)! + +## Updating your Pull Request: How-to Info +We might ask you to edit your pull request before including it, due to spelling errors or because your PR didn't follow the guidelines. [Here](https://github.com/RichardLitt/docs/blob/master/amending-a-commit-guide.md) is a write-up on how to change a pull request. diff --git a/Case-Studies.md b/Case-Studies.md new file mode 100644 index 0000000..2734fee --- /dev/null +++ b/Case-Studies.md @@ -0,0 +1,19 @@ +## Case Studies + +- [Case Study : When emulating Scaling Agile at Spotify went awry at Refinery29](https://medium.com/@andy.park/when-emulating-scaling-agile-at-spotify-goes-awry-d297dc006763) - by Andy Park. Refinery29 case sudy + +- [Fitbit’s Agile Development Journey](http://www.scaledagileframework.com/fitbit-case-study/) - Fitbit case study + +- [Large Scale Agile Transformation in an On-Demand World](https://www.slideshare.net/sgreene/large-scale-agile-transformation-presentation) - by Steve Greene. Salesforce.com case study + +- [LEGO® applies its own approach of “systematic creativity” to adopting SAFe](http://www.scaledagileframework.com/lego-case-study/) - LEGO case study + +- [Royal Philips Cuts Release Cycle Time by Two-Thirds with SAFe](http://www.scaledagileframework.com/royal-phillips-case-study/) - Philips case study + +- [SAFe drives continuous delivery, improves quality, productivity, and employee satisfaction](http://www.scaledagileframework.com/cisco-case-study/) - Cisco case study + +- [Scaling Agile @ Spotify with Tribes, Squads, Chapters & Guilds](http://blog.crisp.se/2012/11/14/henrikkniberg/scaling-agile-at-spotify) - by Henrik Kniberg. Spotify case study + +- [Scaling Agile Across the Enterprise](http://stories.visualstudio.com/scaling-agile-across-the-enterprise/) - Microsoft Visual Studio case study + +- [Staying Ahead of Moore’s Law Intel MVE Delivers 65% More Product Variants](http://www.scaledagileframework.com/case-study-intel/) - Intel case study \ No newline at end of file diff --git a/Code-Review.md b/Code-Review.md new file mode 100644 index 0000000..afed493 --- /dev/null +++ b/Code-Review.md @@ -0,0 +1,5 @@ +## Code Review + +- [Code Reviews in an Agile, Fast-Paced Environment](https://hackernoon.com/code-reviews-in-an-agile-fast-paced-environment-464d5e6ec860) - by Farnoosh Azadi + +- [What We Learned from Google: Code Reviews Aren’t Just for Catching Bugs](https://blog.fullstory.com/what-we-learned-from-google-code-reviews-arent-just-for-catching-bugs/) - by Bruce Johnson \ No newline at end of file diff --git a/Continuous-Delivery.md b/Continuous-Delivery.md new file mode 100644 index 0000000..20899a7 --- /dev/null +++ b/Continuous-Delivery.md @@ -0,0 +1,5 @@ +## Continuous Delivery + +- [Build Quality In: The Key to Continuous Delivery in Kanban](https://leankit.com/blog/2016/10/build-quality-key-continuous-delivery/) - by Gus Evangelisti + +- [Continuous Delivery Distilled](https://www.slideshare.net/mcallana/continuous-delivery-distilled) - by Matt Callanan \ No newline at end of file diff --git a/Daily-Standup-Meeting.md b/Daily-Standup-Meeting.md new file mode 100644 index 0000000..bee5b45 --- /dev/null +++ b/Daily-Standup-Meeting.md @@ -0,0 +1,5 @@ +## Daily Standup Meeting + +- [16 Stand-up Anti-Patterns Threatening Your Transition to Scrum](https://age-of-product.com/stand-up-anti-patterns/) + +- [It's Not Just Standing Up: Patterns for Daily Standup Meetings](https://martinfowler.com/articles/itsNotJustStandingUp.html) - by Jason Yip \ No newline at end of file diff --git a/Decisions.md b/Decisions.md new file mode 100644 index 0000000..34f8133 --- /dev/null +++ b/Decisions.md @@ -0,0 +1,7 @@ +## Decisions + +- [Decider Protocol](https://www.darkcoding.net/behaviour/decider-protocol/) - by Graham King + +- [Decisions, Decisions](https://www.youtube.com/watch?v=EauykEv_2iA) - by Dan North (Video) + +- [Open Decision Framework](https://github.com/red-hat-people-team/open-decision-framework/blob/master/ODF-community.pdf) \ No newline at end of file diff --git a/Definition-of-Done.md b/Definition-of-Done.md new file mode 100644 index 0000000..969ac3f --- /dev/null +++ b/Definition-of-Done.md @@ -0,0 +1,5 @@ +## Definition of Done + +- [Agile and The Definition of Done : Why it Matters?](https://www.linkedin.com/pulse/agile-definition-done-why-matters-dhaval-panchal) - by Dhaval Panchal + +- [Why Getting to Done Is So Important](https://www.mountaingoatsoftware.com/blog/why-getting-to-done-is-so-important) - by Mike Cohn \ No newline at end of file diff --git a/Domain-Driven-Design-DDD.md b/Domain-Driven-Design-DDD.md new file mode 100644 index 0000000..6f4816d --- /dev/null +++ b/Domain-Driven-Design-DDD.md @@ -0,0 +1,3 @@ +## Domain Driven Design (DDD) + +- [Modelling Reactive Systems with Event Storming and Domain-Driven Design](https://blog.redelastic.com/corporate-arts-crafts-modelling-reactive-systems-with-event-storming-73c6236f5dd7) - by Kevin Webber \ No newline at end of file diff --git a/Epic.md b/Epic.md new file mode 100644 index 0000000..eb50a0d --- /dev/null +++ b/Epic.md @@ -0,0 +1,5 @@ +## Epic + +- [Epic Confusion](https://www.agilealliance.org/epic-confusion/) - by Kent McDonald + +- [Stories and Epics](https://hackernoon.com/stories-vs-epics-d773118420d2) - by John Cutler \ No newline at end of file diff --git a/Estimation.md b/Estimation.md new file mode 100644 index 0000000..40b6219 --- /dev/null +++ b/Estimation.md @@ -0,0 +1,17 @@ +## Estimation + +- [Accuratizing Software Estimation](https://medium.com/pointer-io/accuratizing-software-estimation-cf81a9e9fd87) - by Chet Haase + +- [Building a Fort: Lessons in Software Estimation](http://www.construx.com/10x_Software_Development/Building_a_Fort__Lessons_in_Software_Estimation/) - by Steve McConnell + +- [Can You Stop Using Story Points?](https://hackernoon.com/can-you-stop-using-story-points-ac36449ffa10) - by John Cutler + +- [Pointing Poker](https://www.pointingpoker.com/) + +- [SE-Radio Episode 273: Steve McConnell on Software Estimation](http://www.se-radio.net/2016/11/se-radio-episode-273-steve-mcconnell-on-software-estimation/) - Podcast + +- [Stop Using Story Points](https://www.industriallogic.com/blog/stop-using-story-points/) - by Joshua Kerievsky + +- [The Practical Realities of Software Estimation](http://www.disciplinedagiledelivery.com/software-guesstimation/) - by Scott Ambler + +- [Why Estimation in Software Development is Usually Terrible](https://m.coderdan.co/why-estimation-in-software-development-is-usually-terrible-2d032161bc6) - by Dan Draper \ No newline at end of file diff --git a/Kanban.md b/Kanban.md new file mode 100644 index 0000000..3eaaff8 --- /dev/null +++ b/Kanban.md @@ -0,0 +1,7 @@ +## Kanban + +- [One Day in Kanban Land](http://blog.crisp.se/2009/06/26/henrikkniberg/1246053060000) - by Henrik Kniberg + +- [Kanban, Can’tban, and Risky Visualizations](https://medium.com/@johnpcutler/kanban-cannotban-and-risky-visualizations-e19d83b53718) - by John Cutler + +- [Tutorial - Tracking a Kanban Team](https://confluence.atlassian.com/agile/jira-agile-user-s-guide/jira-agile-tutorials/tutorial-tracking-a-kanban-team) \ No newline at end of file diff --git a/Lean.md b/Lean.md new file mode 100644 index 0000000..74311f5 --- /dev/null +++ b/Lean.md @@ -0,0 +1,17 @@ +## Lean + +- [5 Lean behaviours we should all practice](https://www.linkedin.com/pulse/5-lean-behaviours-we-should-all-practice-james-morgan) - by James Morgan + +- [7 Lean Metrics to Improve Flow](https://leankit.com/learn/kanban/lean-flow-metrics/) + +- [Enter The Matrix – Lean Prioritisation](https://www.mindtheproduct.com/2017/07/enter-matrix-lean-prioritisation/) - by Andy Wicks + +- [Lean Coffee in the Workplace](http://agilecoffee.com/lean-coffee-in-the-workplace/) - by Victor ‘Vic’ Bonacci + +- [Lean Enterprise: How High Performance Organizations Innovate at Scale](http://barryoreilly.com/lean-enterprise/) - by Jez Humble, Joanne Molesky and Barry O’Reilly + +- [Lean UX: Applying Lean Principles to Improve User Experience](http://www.jeffgothelf.com/lean-ux-book/) - by Jeff Gothelf with Josh Seiden + +- [Running Lean: Iterate from Plan A to a Plan That Works](http://shop.oreilly.com/product/0636920020141.do) - by Ash Maurya + +- [The Lean Startup: How Today’s Entrepreneurs Use Continuous Innovation to Create Radically Successful Businesses](http://theleanstartup.com/book) - by Eric Ries \ No newline at end of file diff --git a/MAINTAINERS.md b/MAINTAINERS.md new file mode 100644 index 0000000..408fa9a --- /dev/null +++ b/MAINTAINERS.md @@ -0,0 +1,3 @@ +## Maintainers + +* [Lora Vardarova](https://www.linkedin.com/in/loravardarova/) diff --git a/Management-3.0.md b/Management-3.0.md new file mode 100644 index 0000000..69db993 --- /dev/null +++ b/Management-3.0.md @@ -0,0 +1,7 @@ +## Management 3.0 + +- [Kudobox](http://kudobox.co/) + +- [Management 3.0 Agile Leadership Practices](https://www.slideshare.net/jurgenappelo/management-30-in-50-minutes) + +- [Management 3.0 Products: Kudo Cards](https://management30.com/product/kudo-cards/) \ No newline at end of file diff --git a/Metrics.md b/Metrics.md new file mode 100644 index 0000000..7e570cf --- /dev/null +++ b/Metrics.md @@ -0,0 +1,9 @@ +## Metrics + +- [Burndown Chart - the Ultimate Guide for Every Scrum Master](https://luis-goncalves.com/burndown-chart-ultimate-guide/) - by Luís Gonçalves + +- [Do you want Crappy Agile? Metrics. Maybe we should just say no.](http://ronjeffries.com/articles/016-03/you-want/) - by Ron Jeffries + +- [Tutorial - Tracking a Kanban Team](https://confluence.atlassian.com/agile/jira-agile-user-s-guide/jira-agile-tutorials/tutorial-tracking-a-kanban-team) + +- [Why Vanity Metrics are Dangerous: Holding a Mirror Up to Your Measures of Success](https://leankit.com/blog/2016/03/why-vanity-metrics-are-dangerous-holding-a-mirror-up-to-your-measures-of-success/) - by Julia Wester \ No newline at end of file diff --git a/Minimum-Viable-Product-MVP.md b/Minimum-Viable-Product-MVP.md new file mode 100644 index 0000000..55f34c6 --- /dev/null +++ b/Minimum-Viable-Product-MVP.md @@ -0,0 +1,5 @@ +## Minimum Viable Product (MVP) + +- [Minimum Valuable Problem](http://tynerblain.com/blog/2016/07/22/minimum-valuable-problem/) - by Scott Sehlhorst + +- [The MVP is dead. Long live the RAT.](https://hackernoon.com/the-mvp-is-dead-long-live-the-rat-233d5d16ab02) - by Rik Higham \ No newline at end of file diff --git a/Objectives-and-Key-Results-OKRs.md b/Objectives-and-Key-Results-OKRs.md new file mode 100644 index 0000000..eaddd89 --- /dev/null +++ b/Objectives-and-Key-Results-OKRs.md @@ -0,0 +1,7 @@ +## Objectives and Key Results (OKRs) + +- [Accomplish Big Goals With Objectives & Key Results](https://www.slideshare.net/futureinsights/accomplish-big-goals-with-objectives-key-results-christina-wodtke) - by Christina Wodtke + +- [Applying OKRs](https://dannorth.net/2017/05/01/applying-okrs/) - by Dan North + +- [Beyond OKRs: The Formula for High Performing Teams](http://eleganthack.com/beyond-okrs-the-formula-for-high-performing-teams/) - by Christina Wodtke \ No newline at end of file diff --git a/Pair-Programming.md b/Pair-Programming.md new file mode 100644 index 0000000..a60f172 --- /dev/null +++ b/Pair-Programming.md @@ -0,0 +1,7 @@ +## Pair Programming + +- [Agile Pair Programming Everything You Need to Know…](https://luis-goncalves.com/agile-pair-programming/) - by Luís Gonçalves + +- [Pairing, Are You Doing it Wrong?](https://www.thoughtworks.com/insights/blog/pairing-are-you-doing-it-wrong) - by Ryan Oglesby + +- [Strengthening the Case for Pair-Programming](http://www.cs.utah.edu/~lwilliam/Papers/ieeeSoftware.PDF) - by Laurie Williams, Robert Kessler, Ward Cunningham and Ron Jeffries diff --git a/Product-Backlog.md b/Product-Backlog.md new file mode 100644 index 0000000..4b94341 --- /dev/null +++ b/Product-Backlog.md @@ -0,0 +1,7 @@ +## Product Backlog + +- [28 Product Backlog and Refinement Anti-Patterns](https://age-of-product.com/28-product-backlog-anti-patterns/) + +- [Product Backlog](https://less.works/less/framework/product-backlog.html) + +- [Scrum Product Backlog – the Ultimate Simplistic Guide](https://luis-goncalves.com/scrum-product-backlog/) - by Luís Gonçalves \ No newline at end of file diff --git a/Product-Management.md b/Product-Management.md new file mode 100644 index 0000000..f6d88fa --- /dev/null +++ b/Product-Management.md @@ -0,0 +1,9 @@ +## Product Management + +- [12 Signs You’re Working in a Feature Factory](https://hackernoon.com/12-signs-youre-working-in-a-feature-factory-44a5b938d6a2) - by John Cutler + +- [7 Brilliant Little Skills To Master Your Role As A Product Manager](https://www.prodpad.com/blog/essential-skills-for-product-manager-roles/) - by Janna Bastow + +- [How to Survive the Hardest Part of Product Management by Janna Bastow](https://www.mindtheproduct.com/2017/09/survive-hardest-part-product-management-janna-bastow/) - by Martin Eriksson + +- [Top 7 Agile Tips I learnt as a Product Manager](https://www.youtube.com/watch?v=v7bNTqMlq-E) - by Benjamin Mitchell (Video) diff --git a/Product-Owner.md b/Product-Owner.md new file mode 100644 index 0000000..04af5b8 --- /dev/null +++ b/Product-Owner.md @@ -0,0 +1,3 @@ +## Product Owner + +- [Agile Product Ownership in a Nutshell](https://www.youtube.com/watch?v=502ILHjX9EE) - by Henrik Kniberg (Video) \ No newline at end of file diff --git a/Retrospectives.md b/Retrospectives.md new file mode 100644 index 0000000..1645fda --- /dev/null +++ b/Retrospectives.md @@ -0,0 +1,34 @@ +## Retrospectives + +- [10 Agile Retrospectives Exercises](https://www.dropbox.com/s/6nedqvit10rvptc/10%20Agile%20Retrospectives%20Exercises_Luis%20Goncalves.pdf) - by Luis Goncalves + +- [11 Ideas to Spice up Your Retrospective](https://www.scrum.org/resources/blog/11-ideas-spice-your-retrospective) - by Barry Overeem + +- [A 5-why root cause analysis retrospective](http://nomad8.com/a-5-why-root-cause-analysis-retrospective/) - by Sandy Mamoli + +- [Agenda and Ideas](https://www.solutionsiq.com/learning/blog-post/agenda-and-ideas/) - by Tony Bonfante + +- [Agile Retrospective Resource Wiki](http://retrospectivewiki.org/index.php?title=Agile_Retrospective_Resource_Wiki) + +- [An Insight into Joint Retrospectives](https://www.scrumalliance.org/community/articles/2014/july/an-insight-into-joint-retrospectives) - by Madhavi Ledalla + +- [Awesome Retrospectives](https://github.com/josephearl/awesome-retrospectives) + +- [Energizing Retrospective – Energize Your Team Retrospective With This Easy Exercise](https://luis-goncalves.com/energize-your-team-retrospective/) - by Luis Goncalves + +- [Fun Retro](http://funretro.github.io/distributed/) + +- [Retromat](https://plans-for-retrospectives.com/) + +- [Retrospective Agile Facilitator Role and Responsibilities](https://luis-goncalves.com/retrospective-agile-facilitator/) - by Luis Goncalves + +- [Retrospective: Do the Team Radar](https://blog.agilistic.nl/retrospective-do-the-team-radar/) - by Christiaan Verwijs + +- [Retrospective Exercises Repository](https://age-of-product.com/retrospective-exercises/) + +- [Return of the Retrospective - Prioritising continuous improvement](https://www.slideshare.net/RyanMcKergow/return-of-the-retrospective-prioritising-continuous-improvement-15122016) - by Ryan McKergow + +- [Technical Debt Wall Retrospective](http://fabiopereira.me/blog/2009/09/01/technical-debt-retrospective/) - by Fabio Pereira + +- [Your Agile Journey with the Backpacking Retrospective Exercise](https://www.benlinders.com/2017/agile-journey-backpacking-retrospective-exercise/) - by Ben Linders + diff --git a/Scrum-Master.md b/Scrum-Master.md new file mode 100644 index 0000000..d8603f9 --- /dev/null +++ b/Scrum-Master.md @@ -0,0 +1,23 @@ +## Scrum Master + +- [70 Scrum Master Theses](https://age-of-product.com/70-scrum-master-theses/) + +- [A Day in the Life of a Scrum Master](https://www.linkedin.com/pulse/day-life-scrum-master-barry-overeem) - by Barry Overeem + +- [A good ScrumMaster is much more than a Team Coach](https://www.linkedin.com/pulse/good-scrummaster-much-more-than-team-coach-iain-mckenna) - by Iain McKenna + +- [A Scrum Master’s Checklist](http://blogs.collab.net/agile/a-scrummasters-checklist) - by Michael James + +- [An Example Checklist for ScrumMasters](http://scrummasterchecklist.org/pdf/ScrumMaster_Checklist_12_unbranded.pdf) + +- [Effective Leadership Styles for Scrum Masters](https://www.benlinders.com/2016/leadership-styles-scrum-masters/) - by Ben Linders + +- [Hiring: 38 Scrum Master Interview Questions to Avoid Agile Imposters](https://age-of-product.com/38-scrum-master-interview-questions-to-avoid-imposters-free-pdf/) + +- [ScrumMaster](https://www.mountaingoatsoftware.com/agile/scrum/roles/scrummaster) + +- [Scrum Training Series](http://scrumtrainingseries.com/) + +- [Three Mistakes Scrum Masters Make and How to Correct Them](https://www.linkedin.com/pulse/three-mistakes-scrum-masters-make-how-correct-them-mike-cohn) - by Mike Cohn + +- [Viewing the Scrum Master as a Team Member](http://www.spikesandstories.com/viewing-scrum-master-team-member/) by Tanner diff --git a/Scrum.md b/Scrum.md new file mode 100644 index 0000000..ea5b317 --- /dev/null +++ b/Scrum.md @@ -0,0 +1,11 @@ +## Scrum + +- [Reasons Why Scrum Can Fail](http://www.scrumexpert.com/knowledge/reasons-why-scrum-can-fail/) + +- [Scaling Scrum – a brief comparison of DAD, LeSS, and SAFe](https://www.linkedin.com/pulse/scaling-scrum-brief-comparison-dad-less-safe-brian-m-rabon-cst-pmp) - by Brian M. Rabon + +- [Scrum, A Brief Look into Using the Scrum Framework for Software Development](https://www.atlassian.com/agile/scrum) + +- [Scrum in 5 Minutes](http://stephenwalther.com/archive/2012/08/17/scrum-in-5-minutes) - by Stephen Walther + +- [The Scrum Guide™](http://www.scrumguides.org/scrum-guide.html) diff --git a/Sprint-Demo.md b/Sprint-Demo.md new file mode 100644 index 0000000..c0e0569 --- /dev/null +++ b/Sprint-Demo.md @@ -0,0 +1,3 @@ +## Sprint Demo + +- [Applying "Build, Measure Learn" principles to Sprint Demos](https://www.linkedin.com/pulse/applying-build-measure-learn-principles-sprint-demos-ryan-thomas) - by Ryan Thomas Hewitt \ No newline at end of file diff --git a/Story-Mapping.md b/Story-Mapping.md new file mode 100644 index 0000000..da6336c --- /dev/null +++ b/Story-Mapping.md @@ -0,0 +1,5 @@ +## Story Mapping + +- [Story Map](https://www.youtube.com/watch?v=wlYEc6Bml5c) - Video + +- [Story Mapping, Visual Way of Building Product Backlog](https://www.thoughtworks.com/insights/blog/story-mapping-visual-way-building-product-backlog) - by Sunit Parekh \ No newline at end of file diff --git a/Story-Splitting.md b/Story-Splitting.md new file mode 100644 index 0000000..1e09315 --- /dev/null +++ b/Story-Splitting.md @@ -0,0 +1,11 @@ +## Story Splitting + +- [10 Powerful Strategies for Breaking down User Stories in Scrum (with Cheatsheet)](https://medium.com/@chrisverwijs/10-powerful-strategies-for-breaking-down-user-stories-in-scrum-with-cheatsheet-2cd9aae7d0eb) - by Christiaan Verwijs + +- [How to Split a User Story](http://agileforall.com/wp-content/uploads/2012/01/Story-Splitting-Flowchart.pdf) + +- [Slicing User Stories, Delivering Value](https://www.linkedin.com/pulse/slicing-user-stories-delivering-value-ellen-gottesdiener) - by Ellen Gottesdiener + +- [Split User Stories Ruthlessly - And Get Value Earlier](http://mikeborozdin.com/post/split-user-stories-get-value-early/) - by Mike Borozdin + +- [Splitting user stories -- the hamburger method](https://gojko.net/2012/01/23/splitting-user-stories-the-hamburger-method/) - by Gojko Adzic \ No newline at end of file diff --git a/Team.md b/Team.md new file mode 100644 index 0000000..78f1e86 --- /dev/null +++ b/Team.md @@ -0,0 +1,49 @@ +## Team + +- [5 Dysfunctions of a Team: Absence of Trust](http://blog.cayenneapps.com/2016/08/17/5-dysfunctions-of-a-team-absence-of-trust/) + +- [5 Exercises That Break Down Barriers](https://www.ideo.com/blog/5-exercises-that-break-down-barriers) + +- [10 New Rules For Brainstorming Without Alienating Introverts](https://www.fastcompany.com/3067769/10-new-rules-for-brainstorming-without-alienating-introverts) - by Judah Pollack and Olivia Fox Cabane + +- [10 Signs of Unsound Agile Individuals](http://theagiletimes.com/10-signs-of-unsound-agile-individuals/) + +- [10 Warning Signs, That Your Team Is Not Self-Organizing](http://www.scrum-breakfast.com/2015/10/10-warning-signs-that-your-team-is-not.html) - by Peter Stevens + +- [Beyond OKRs: The Formula for High Performing Teams](http://eleganthack.com/beyond-okrs-the-formula-for-high-performing-teams/) - by Christina Wodtke + +- [Building a self-organized team in a radically agile company.](https://jobs.zalando.com/tech/blog/building-a-self-organized-team-in-a-radically-agile-company./) - by Matthias Kunze and Himanshu Sharma + +- [Fear Has to Go for Agile Teams To Succeed](https://www.linkedin.com/pulse/fear-has-go-agile-teams-succeed-anthony-mersino) - by Anthony Mersino + +- [Feedback for Teams](https://medium.com/the-creative-founder/feedback-for-teams-b2696661ddf7) - by Christina Wodtke + +- [Good Product Team / Bad Product Team](https://svpg.com/good-product-team-bad-product-team/) - by Marty Cagan + +- [How to Align Scrum Teams](https://dzone.com/articles/how-to-align-scrum-teams) - by Stefan Wolpers + +- [How to Build a High Velocity Development Team](https://medium.com/javascript-scene/how-to-build-a-high-velocity-development-team-4b2360d34021) - by Eric Elliott + +- [How To Build An Agile Team](https://www.madetech.com/blog/how-to-build-an-agile-team) - by Luke Morton + +- [How To Kickstart A Great Scrum Team (10 practical things to do)](https://www.linkedin.com/pulse/how-kickstart-great-scrum-team-10-practical-things-do-verwijs) - by Christiaan Verwijs + +- [How to Tell Whether Your Team is Agile](https://www.linkedin.com/pulse/how-tell-whether-your-team-agile-gil-broza) - by Gil Broza + +- [Let Your Teams Plan for Themselves](https://www.madetech.com/blog/let-your-teams-plan-for-themselves) - by Luke Morton + +- [Of Arguments and Agile](https://www.scrumalliance.org/community/articles/2017/august/of-arguments-and-agile) + +- [Scrum Myths 10 - Non-Scrum Roles by Mishkin Berteig Scrum Expert](https://www.youtube.com/watch?v=gUU0_Z3dub8) - Video + +- [Storm To Perform: The 4 Stages Of Team Productivity](https://blog.trello.com/form-storm-norm-perform-stages-of-team-productivity) - by Leah Ryder + +- [The 10 Practices of Healthy Engineering Teams](https://blog.carbonfive.com/2016/02/17/the-10-practices-of-healthy-engineering-teams-part-1/) - by Andrew Hao + +- [The Best Teams Hold Themselves Accountable](https://hbr.org/2014/05/the-best-teams-hold-themselves-accountable) - by Joseph Grenny + +- [There are no True Scrum Teams](https://www.linkedin.com/pulse/true-scrum-teams-michael-k%C3%BCsters) - by Michael Küsters + +- [Trust, Diversity, And Passion—The 3 Ingredients Of Successful Organizations](https://www.linkedin.com/pulse/trust-diversity-passion-three-ingredients-successful-richard-bliss) - by Richard Bliss + +- [What Is a Team?](https://less.works/less/structure/teams.html) \ No newline at end of file diff --git a/Technical-Debt.md b/Technical-Debt.md new file mode 100644 index 0000000..5dca383 --- /dev/null +++ b/Technical-Debt.md @@ -0,0 +1,7 @@ +## Technical-Debt + +- [Dealing with Technical Debt Like We Mean it](https://medium.com/@GeneHughson/dealing-with-technical-debt-like-we-mean-it-155a98a39f1c) - by Gene Hughson + +- [You’re Using “Technical Debt” Wrong](https://www.solutionsiq.com/resource/agile-amped-podcast/doc-norton-sez-youre-using-technical-debt-wrong-at-agile2016/) - Video + +- [Technical Debt Wall Retrospective](http://fabiopereira.me/blog/2009/09/01/technical-debt-retrospective/) - by Fabio Pereira \ No newline at end of file diff --git a/Test-Driven-Development-TDD.md b/Test-Driven-Development-TDD.md new file mode 100644 index 0000000..7b8db43 --- /dev/null +++ b/Test-Driven-Development-TDD.md @@ -0,0 +1,3 @@ +## Test Driven Development (TDD) + +- [Test Driven Development: By Example](https://www.amazon.com/Test-Driven-Development-Kent-Beck/dp/0321146530/) - by Kent Beck \ No newline at end of file diff --git a/User-Stories.md b/User-Stories.md new file mode 100644 index 0000000..cd064c9 --- /dev/null +++ b/User-Stories.md @@ -0,0 +1,7 @@ +## User Stories + +- [“As a user” needs to stop.](https://blog.prototypr.io/stop-it-with-as-a-user-5feb9b38d920) - by Janet Taylor + +- [Designing features using Job Stories](https://blog.intercom.com/using-job-stories-design-features-ui-ux/) - by Alan Klement + +- [Stories and Epics](https://hackernoon.com/stories-vs-epics-d773118420d2) - by John Cutler \ No newline at end of file diff --git a/code-of-conduct.md b/code-of-conduct.md new file mode 100644 index 0000000..821cb8e --- /dev/null +++ b/code-of-conduct.md @@ -0,0 +1,74 @@ +# Contributor Covenant Code of Conduct + +## Our Pledge + +In the interest of fostering an open and welcoming environment, we as +contributors and maintainers pledge to making participation in our project and +our community a harassment-free experience for everyone, regardless of age, body +size, disability, ethnicity, gender identity and expression, level of experience, +nationality, personal appearance, race, religion, or sexual identity and +orientation. + +## Our Standards + +Examples of behaviour that contributes to creating a positive environment +include: + +* Using welcoming and inclusive language +* Being respectful of differing viewpoints and experiences +* Gracefully accepting constructive criticism +* Focusing on what is best for the community +* Showing empathy towards other community members + +Examples of unacceptable behaviour by participants include: + +* The use of sexualised language or imagery and unwelcome sexual attention or +advances +* Trolling, insulting/derogatory comments, and personal or political attacks +* Public or private harassment +* Publishing others' private information, such as a physical or electronic + address, without explicit permission +* Other conduct which could reasonably be considered inappropriate in a + professional setting + +## Our Responsibilities + +Project maintainers are responsible for clarifying the standards of acceptable +behaviour and are expected to take appropriate and fair corrective action in +response to any instances of unacceptable behaviour. + +Project maintainers have the right and responsibility to remove, edit, or +reject comments, commits, code, wiki edits, issues, and other contributions +that are not aligned to this Code of Conduct, or to ban temporarily or +permanently any contributor for other behaviours that they deem inappropriate, +threatening, offensive, or harmful. + +## Scope + +This Code of Conduct applies both within project spaces and in public spaces +when an individual is representing the project or its community. Examples of +representing a project or community include using an official project e-mail +address, posting via an official social media account, or acting as an appointed +representative at an online or offline event. Representation of a project may be +further defined and clarified by project maintainers. + +## Enforcement + +Instances of abusive, harassing, or otherwise unacceptable behaviour may be +reported by contacting the project team at lorabv@gmail.com. All +complaints will be reviewed and investigated and will result in a response that +is deemed necessary and appropriate to the circumstances. The project team is +obligated to maintain confidentiality with regard to the reporter of an incident. +Further details of specific enforcement policies may be posted separately. + +Project maintainers who do not follow or enforce the Code of Conduct in good +faith may face temporary or permanent repercussions as determined by other +members of the project's leadership. + +## Attribution + +This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, +available at [http://contributor-covenant.org/version/1/4][version] + +[homepage]: http://contributor-covenant.org +[version]: http://contributor-covenant.org/version/1/4/