Are you over 18 and want to see adult content?
More Annotations
A complete backup of https://androidlegend.com
Are you over 18 and want to see adult content?
A complete backup of https://neobienetre.fr
Are you over 18 and want to see adult content?
A complete backup of https://universitas.no
Are you over 18 and want to see adult content?
A complete backup of https://mariokarttour.com
Are you over 18 and want to see adult content?
A complete backup of https://vw-avtoruss.ru
Are you over 18 and want to see adult content?
A complete backup of https://elconfidencialdigital.com
Are you over 18 and want to see adult content?
A complete backup of https://genericviagra4u-totreat.com
Are you over 18 and want to see adult content?
A complete backup of https://northwesternmutual.com
Are you over 18 and want to see adult content?
A complete backup of https://smartypot.ir
Are you over 18 and want to see adult content?
A complete backup of https://turisvalencia.es
Are you over 18 and want to see adult content?
A complete backup of https://blackillustrations.com
Are you over 18 and want to see adult content?
Favourite Annotations
A complete backup of http://www.urlrate.net/www/lmsins.ir
Are you over 18 and want to see adult content?
A complete backup of https://www.mutaz.net/free-programs/en/download/?1135
Are you over 18 and want to see adult content?
A complete backup of https://tunein.com/
Are you over 18 and want to see adult content?
A complete backup of https://units.bmi.ir/fa/Unit.aspx?id=3700
Are you over 18 and want to see adult content?
A complete backup of https://world.new7wonders.com/
Are you over 18 and want to see adult content?
A complete backup of https://www.imdb.com/title/tt7224504/
Are you over 18 and want to see adult content?
A complete backup of https://jthnx5wyvjvzsxtu.onion.ly/dpr/res/652.html
Are you over 18 and want to see adult content?
A complete backup of https://chasek8.wordpress.com/tag/parents/
Are you over 18 and want to see adult content?
A complete backup of https://trymobile.ru/
Are you over 18 and want to see adult content?
A complete backup of https://greatsouthernworkshops.weebly.com/
Are you over 18 and want to see adult content?
Text
THE SYSTEM METAPHOR
MULTI-LEVEL STORIES
Stories Have Multiple Granularities. User stories may seem like they are about specifications but they’re really a lightweight way to explore possibilities. Many teams get too focused on the “card” aspect, using tools to turn user stories into an atomized requirements spec. Instead, we can use stories to think fluidly at multiple levels. SPECULATIVE GENERALITY INVEST IN GOOD STORIES, AND SMART TASKS As you discuss stories, write cards, and split stories, the INVEST acronym can help remind you of characteristics of good stories. When creating a task plan, applying the SMART acronym can improve yourtasks.
SPEECH: METAPHORS FOR EXTREME PROGRAMMING (XP) Test-first, or test-driven development, is one of XP’s fundamental design techniques. It works like this: 1. Write a test, which probably can’t even compile because you haven’t written any real code yet. 2. Implement a stub of the feature, so the test runs but fails. 3. CHARTERING AND MORE: WHAT HAPPENS BEFORE USER STORIES?XP RADAR CHART
AUTHORIZATION
Authorization is the process of deciding whether to allow a user can access or use some resource. (Don’t confuse it with authentication, the process of deciding whether a user is who they claim to be.). TDD and Authorization. From a TDD perspective, there are two core tests: that an authorized user can do something, and that an unauthorizeduser cannot.
TWENTY WAYS TO SPLIT STORIES 1. Hardware architects have a “0, 1, infinity” rule – these are the easiest three values to handle. Special cases bring in issues of resource management. 1. Many. It’s usually easiest to get one right and then move to a collection. Split condition. Full condition. Treat “and,” “or,” and “then” and other connector words as EXAMPLES OF USER STORIES 2020 What we have instead is more of a punchlist – a list of tasks to be done. But some of those tasks are user stories as well. Each row has “state” (Keystone, Blocked, Todo, In Progress, or Done) and “who will do what by when”. Most of the things on there are tasks: “Investigate blank screen on first use”, “Set up ad service”.THE SYSTEM METAPHOR
MULTI-LEVEL STORIES
Stories Have Multiple Granularities. User stories may seem like they are about specifications but they’re really a lightweight way to explore possibilities. Many teams get too focused on the “card” aspect, using tools to turn user stories into an atomized requirements spec. Instead, we can use stories to think fluidly at multiple levels. SPECULATIVE GENERALITY INVEST IN GOOD STORIES, AND SMART TASKS As you discuss stories, write cards, and split stories, the INVEST acronym can help remind you of characteristics of good stories. When creating a task plan, applying the SMART acronym can improve yourtasks.
SPEECH: METAPHORS FOR EXTREME PROGRAMMING (XP) Test-first, or test-driven development, is one of XP’s fundamental design techniques. It works like this: 1. Write a test, which probably can’t even compile because you haven’t written any real code yet. 2. Implement a stub of the feature, so the test runs but fails. 3. CHARTERING AND MORE: WHAT HAPPENS BEFORE USER STORIES?XP RADAR CHART
AUTHORIZATION
Authorization is the process of deciding whether to allow a user can access or use some resource. (Don’t confuse it with authentication, the process of deciding whether a user is who they claim to be.). TDD and Authorization. From a TDD perspective, there are two core tests: that an authorized user can do something, and that an unauthorizeduser cannot.
TWENTY WAYS TO SPLIT STORIES 1. Hardware architects have a “0, 1, infinity” rule – these are the easiest three values to handle. Special cases bring in issues of resource management. 1. Many. It’s usually easiest to get one right and then move to a collection. Split condition. Full condition. Treat “and,” “or,” and “then” and other connector words as SPECULATIVE GENERALITY Speculative Generality. Speculative generality is guessing about the future, subject to the challenges that brings. With software, there’s little call to repeat projects: “Let’s rewrite this in the same language, with the same design, using the same tools, and targeting exactly the same platform!”. Instead, we work in achanging world.
REVISE TESTS WHILE REFACTORING? IT DEPENDS Some refactorings (e.g., Extract Method or Extract Class) introduce new elements. Should you revise the tests to take these into account? The classic consultant’s answer applies: It depends. LEAN MANUFACTURING AND SOFTWARE Is writing software more like manufacturing cookies or more like designing cookie cutters? It's easy to wish that we could develop software like a factory stamps out cookies, but software has a design or creation element that is missing in that analogy. Lean manufacturing is a different approach than a traditional assembly line, and offers some lessons for software development.AUTHORIZATION
Authorization is the process of deciding whether to allow a user can access or use some resource. (Don’t confuse it with authentication, the process of deciding whether a user is who they claim to be.). TDD and Authorization. From a TDD perspective, there are two core tests: that an authorized user can do something, and that an unauthorizeduser cannot.
TWENTY WAYS TO SPLIT STORIES 1. Hardware architects have a “0, 1, infinity” rule – these are the easiest three values to handle. Special cases bring in issues of resource management. 1. Many. It’s usually easiest to get one right and then move to a collection. Split condition. Full condition. Treat “and,” “or,” and “then” and other connector words as TESTABLE STORIES IN THE INVEST MODEL T is for Testable in the INVEST model. A testable story is one for which, given any inputs, we can agree on the expected system behavior and/or outputs. Bonus: INVEST ebook Get "INVEST in Good Stories: The Series", a 40-page ebook with key INVEST articlesall in one place.
ZERO-ONE-MANY IN TEST-DRIVEN DEVELOPMENT The Zero-One-Many principle is also known as “Zero-One-Infinity” as well, and has been around for a while. Zero-One-Many. In Test-Driven Development, Zero-One-Many says that the easiest case is (usually) zero of something, the next easiest is one, and the hardest and most general is many.XP ON ONE PAGE
XP on One Page. Posted on February 26, 2002 by Bill Wake. This mini-poster serves as a reminder about most aspects of XP. Poster: XP on One Page (PDF), French. Thanks to Laurent Bossavit, Alex Chaffee, George Dinwiddie, Alan Francis, Ed Hughes, Ron Jeffries, Paul Moore, Ilja Preuss, and Bob Worth. I appreciated their suggestions even if Ididn
100 IMPEDIMENTS
100 Impediments. Posted on August 21, 2009 by Bill Wake. One of the most important things a ScrumMaster does is recognize and remove impediments. This summary sheet includes 100 impediments (PDF) you may run into (though hopefully not all at once:). . REVIEW: IT CAN'T HAPPEN HERE Review: It Can’t Happen Here. It Can’t Happen Here, by Sinclair Lewis, 1935. ISBN 0451465644. This story tells how fascism could come to America. Lewis wrote it in 1935 – before Hitler attacked Poland in 1939. It shows that it was not too early to predict the rise and some of the consequences of fascism. I was surprised that both EXAMPLES OF USER STORIES 2020 What we have instead is more of a punchlist – a list of tasks to be done. But some of those tasks are user stories as well. Each row has “state” (Keystone, Blocked, Todo, In Progress, or Done) and “who will do what by when”. Most of the things on there are tasks: “Investigate blank screen on first use”, “Set up ad service”.THE SYSTEM METAPHOR
MULTI-LEVEL STORIES
Stories Have Multiple Granularities. User stories may seem like they are about specifications but they’re really a lightweight way to explore possibilities. Many teams get too focused on the “card” aspect, using tools to turn user stories into an atomized requirements spec. Instead, we can use stories to think fluidly at multiple levels. SPECULATIVE GENERALITY INVEST IN GOOD STORIES, AND SMART TASKS As you discuss stories, write cards, and split stories, the INVEST acronym can help remind you of characteristics of good stories. When creating a task plan, applying the SMART acronym can improve yourtasks.
SPEECH: METAPHORS FOR EXTREME PROGRAMMING (XP) Test-first, or test-driven development, is one of XP’s fundamental design techniques. It works like this: 1. Write a test, which probably can’t even compile because you haven’t written any real code yet. 2. Implement a stub of the feature, so the test runs but fails. 3. CHARTERING AND MORE: WHAT HAPPENS BEFORE USER STORIES?XP RADAR CHART
AUTHORIZATION
Authorization is the process of deciding whether to allow a user can access or use some resource. (Don’t confuse it with authentication, the process of deciding whether a user is who they claim to be.). TDD and Authorization. From a TDD perspective, there are two core tests: that an authorized user can do something, and that an unauthorizeduser cannot.
TWENTY WAYS TO SPLIT STORIES 1. Hardware architects have a “0, 1, infinity” rule – these are the easiest three values to handle. Special cases bring in issues of resource management. 1. Many. It’s usually easiest to get one right and then move to a collection. Split condition. Full condition. Treat “and,” “or,” and “then” and other connector words as EXAMPLES OF USER STORIES 2020 What we have instead is more of a punchlist – a list of tasks to be done. But some of those tasks are user stories as well. Each row has “state” (Keystone, Blocked, Todo, In Progress, or Done) and “who will do what by when”. Most of the things on there are tasks: “Investigate blank screen on first use”, “Set up ad service”.THE SYSTEM METAPHOR
MULTI-LEVEL STORIES
Stories Have Multiple Granularities. User stories may seem like they are about specifications but they’re really a lightweight way to explore possibilities. Many teams get too focused on the “card” aspect, using tools to turn user stories into an atomized requirements spec. Instead, we can use stories to think fluidly at multiple levels. SPECULATIVE GENERALITY INVEST IN GOOD STORIES, AND SMART TASKS As you discuss stories, write cards, and split stories, the INVEST acronym can help remind you of characteristics of good stories. When creating a task plan, applying the SMART acronym can improve yourtasks.
SPEECH: METAPHORS FOR EXTREME PROGRAMMING (XP) Test-first, or test-driven development, is one of XP’s fundamental design techniques. It works like this: 1. Write a test, which probably can’t even compile because you haven’t written any real code yet. 2. Implement a stub of the feature, so the test runs but fails. 3. CHARTERING AND MORE: WHAT HAPPENS BEFORE USER STORIES?XP RADAR CHART
AUTHORIZATION
Authorization is the process of deciding whether to allow a user can access or use some resource. (Don’t confuse it with authentication, the process of deciding whether a user is who they claim to be.). TDD and Authorization. From a TDD perspective, there are two core tests: that an authorized user can do something, and that an unauthorizeduser cannot.
TWENTY WAYS TO SPLIT STORIES 1. Hardware architects have a “0, 1, infinity” rule – these are the easiest three values to handle. Special cases bring in issues of resource management. 1. Many. It’s usually easiest to get one right and then move to a collection. Split condition. Full condition. Treat “and,” “or,” and “then” and other connector words as SPECULATIVE GENERALITY Speculative Generality. Speculative generality is guessing about the future, subject to the challenges that brings. With software, there’s little call to repeat projects: “Let’s rewrite this in the same language, with the same design, using the same tools, and targeting exactly the same platform!”. Instead, we work in achanging world.
REVISE TESTS WHILE REFACTORING? IT DEPENDS Some refactorings (e.g., Extract Method or Extract Class) introduce new elements. Should you revise the tests to take these into account? The classic consultant’s answer applies: It depends. LEAN MANUFACTURING AND SOFTWARE Is writing software more like manufacturing cookies or more like designing cookie cutters? It's easy to wish that we could develop software like a factory stamps out cookies, but software has a design or creation element that is missing in that analogy. Lean manufacturing is a different approach than a traditional assembly line, and offers some lessons for software development.AUTHORIZATION
Authorization is the process of deciding whether to allow a user can access or use some resource. (Don’t confuse it with authentication, the process of deciding whether a user is who they claim to be.). TDD and Authorization. From a TDD perspective, there are two core tests: that an authorized user can do something, and that an unauthorizeduser cannot.
TWENTY WAYS TO SPLIT STORIES 1. Hardware architects have a “0, 1, infinity” rule – these are the easiest three values to handle. Special cases bring in issues of resource management. 1. Many. It’s usually easiest to get one right and then move to a collection. Split condition. Full condition. Treat “and,” “or,” and “then” and other connector words as TESTABLE STORIES IN THE INVEST MODEL T is for Testable in the INVEST model. A testable story is one for which, given any inputs, we can agree on the expected system behavior and/or outputs. Bonus: INVEST ebook Get "INVEST in Good Stories: The Series", a 40-page ebook with key INVEST articlesall in one place.
ZERO-ONE-MANY IN TEST-DRIVEN DEVELOPMENT The Zero-One-Many principle is also known as “Zero-One-Infinity” as well, and has been around for a while. Zero-One-Many. In Test-Driven Development, Zero-One-Many says that the easiest case is (usually) zero of something, the next easiest is one, and the hardest and most general is many.XP ON ONE PAGE
XP on One Page. Posted on February 26, 2002 by Bill Wake. This mini-poster serves as a reminder about most aspects of XP. Poster: XP on One Page (PDF), French. Thanks to Laurent Bossavit, Alex Chaffee, George Dinwiddie, Alan Francis, Ed Hughes, Ron Jeffries, Paul Moore, Ilja Preuss, and Bob Worth. I appreciated their suggestions even if Ididn
100 IMPEDIMENTS
100 Impediments. Posted on August 21, 2009 by Bill Wake. One of the most important things a ScrumMaster does is recognize and remove impediments. This summary sheet includes 100 impediments (PDF) you may run into (though hopefully not all at once:). . REVIEW: IT CAN'T HAPPEN HERE Review: It Can’t Happen Here. It Can’t Happen Here, by Sinclair Lewis, 1935. ISBN 0451465644. This story tells how fascism could come to America. Lewis wrote it in 1935 – before Hitler attacked Poland in 1939. It shows that it was not too early to predict the rise and some of the consequences of fascism. I was surprised that both EXAMPLES OF USER STORIES 2020 Here are some examples of user stories for four different systems: a game, a festival manager, a mobile app, and a data viewer. INVEST IN GOOD STORIES, AND SMART TASKS In XP, we think of requirements of coming in the form of user stories. It would be easy to mistake the story card for the “whole story,” but Ron Jeffries points out that stories in XP have three components: Cards (their physical medium), Conversation (the discussion surrounding them), and Confirmation (tests that verify them).MULTI-LEVEL STORIES
User stories are more than detailed specifications. Different levels of stories can help you explore what and why as well as how. SPECULATIVE GENERALITYXP RADAR CHART
CHARTERING AND MORE: WHAT HAPPENS BEFORE USER STORIES? NEGOTIABLE STORIES IN THE INVEST MODELAUTHORIZATION
Authorization is the process of deciding whether to allow a user can access or use some resource. (Don’t confuse it with authentication, the process of deciding whether a user is who they claim to be.). TDD and Authorization. From a TDD perspective, there are two core tests: that an authorized user can do something, and that an unauthorizeduser cannot.
SPEECH: METAPHORS FOR EXTREME PROGRAMMING (XP) Metaphors for XP itself. Continue reading Speech: Metaphors for Extreme Programming (XP)→ TWENTY WAYS TO SPLIT STORIES The ability to split stories is an important skill for customers and developers on XP teams. This note suggests a number of dimensions along which you might divide your stories. EXAMPLES OF USER STORIES 2020 Here are some examples of user stories for four different systems: a game, a festival manager, a mobile app, and a data viewer. INVEST IN GOOD STORIES, AND SMART TASKS In XP, we think of requirements of coming in the form of user stories. It would be easy to mistake the story card for the “whole story,” but Ron Jeffries points out that stories in XP have three components: Cards (their physical medium), Conversation (the discussion surrounding them), and Confirmation (tests that verify them).MULTI-LEVEL STORIES
User stories are more than detailed specifications. Different levels of stories can help you explore what and why as well as how. SPECULATIVE GENERALITYXP RADAR CHART
CHARTERING AND MORE: WHAT HAPPENS BEFORE USER STORIES? NEGOTIABLE STORIES IN THE INVEST MODELAUTHORIZATION
Authorization is the process of deciding whether to allow a user can access or use some resource. (Don’t confuse it with authentication, the process of deciding whether a user is who they claim to be.). TDD and Authorization. From a TDD perspective, there are two core tests: that an authorized user can do something, and that an unauthorizeduser cannot.
SPEECH: METAPHORS FOR EXTREME PROGRAMMING (XP) Metaphors for XP itself. Continue reading Speech: Metaphors for Extreme Programming (XP)→ TWENTY WAYS TO SPLIT STORIES The ability to split stories is an important skill for customers and developers on XP teams. This note suggests a number of dimensions along which you might divide your stories.XP RADAR CHART
Introduction. This scoring sheet and chart combination is designed to help you assess where you are as a team, in doing the “vanilla”practices of XP.
REVISE TESTS WHILE REFACTORING? IT DEPENDS Some refactorings (e.g., Extract Method or Extract Class) introduce new elements. Should you revise the tests to take these into account? The classic consultant’s answer applies: It depends.AUTHORIZATION
Authorization is the process of deciding whether to allow a user can access or use some resource. (Don’t confuse it with authentication, the process of deciding whether a user is who they claim to be.). TDD and Authorization. From a TDD perspective, there are two core tests: that an authorized user can do something, and that an unauthorizeduser cannot.
LEAN MANUFACTURING AND SOFTWARE Is writing software more like manufacturing cookies or more like designing cookie cutters? It's easy to wish that we could develop software like a factory stamps out cookies, but software has a design or creation element that is missing in that analogy. Lean manufacturing is a different approach than a traditional assembly line, and offers some lessons for software development.100 IMPEDIMENTS
This summary sheet includes 100 impediments (PDF) you may run into (though hopefully not all at once:). .. I was inspired to start this list years ago from an article by Barry Boehm (which I’ve since lost and can’t even find a TESTABLE STORIES IN THE INVEST MODEL T is for Testable in the INVEST model. A testable story is one for which, given any inputs, we can agree on the expected system behavior and/or outputs. Bonus: INVEST ebook Get "INVEST in Good Stories: The Series", a 40-page ebook with key INVEST articlesall in one place.
ZERO-ONE-MANY IN TEST-DRIVEN DEVELOPMENT The Zero-One-Many principle is also known as “Zero-One-Infinity” as well, and has been around for a while. Zero-One-Many. In Test-Driven Development, Zero-One-Many says that the easiest case is (usually) zero of something, the next easiest is one, and the hardest and most general is many.MOVIE RETROSPECTIVE
When I'm teaching about retrospectives, there has always been a challenge: a simulated retrospective wants a shared experience. But what shared experience to use? The one experience I know we share is the session we're in, but using a retrospective Continue reading MovieRetrospective→
TWENTY WAYS TO SPLIT STORIES The ability to split stories is an important skill for customers and developers on XP teams. This note suggests a number of dimensions along which you might divide your stories. REVIEW: IT CAN'T HAPPEN HERE It Can’t Happen Here, by Sinclair Lewis, 1935.ISBN 0451465644. This story tells how fascism could come to America. Lewis wrote it in 1935 – before Hitler attacked Poland in 1939.MULTI-LEVEL STORIES
Stories Have Multiple Granularities. User stories may seem like they are about specifications but they’re really a lightweight way to explore possibilities. Many teams get too focused on the “card” aspect, using tools to turn user stories into an atomized requirements spec. Instead, we can use stories to think fluidly at multiple levels. INVEST IN GOOD STORIES, AND SMART TASKS As you discuss stories, write cards, and split stories, the INVEST acronym can help remind you of characteristics of good stories. When creating a task plan, applying the SMART acronym can improve yourtasks.
XP RADAR CHART
THE SYSTEM METAPHOR
REVISE TESTS WHILE REFACTORING? IT DEPENDS Some refactorings (e.g., Extract Method or Extract Class) introduce new elements. Should you revise the tests to take these into account? The classic consultant’s answer applies: It depends. LEAN MANUFACTURING AND SOFTWARE SPEECH: METAPHORS FOR EXTREME PROGRAMMING (XP) Test-first, or test-driven development, is one of XP’s fundamental design techniques. It works like this: 1. Write a test, which probably can’t even compile because you haven’t written any real code yet. 2. Implement a stub of the feature, so the test runs but fails. 3.XP ON ONE PAGE
XP on One Page. Posted on February 26, 2002 by Bill Wake. This mini-poster serves as a reminder about most aspects of XP. Poster: XP on One Page (PDF), French. Thanks to Laurent Bossavit, Alex Chaffee, George Dinwiddie, Alan Francis, Ed Hughes, Ron Jeffries, Paul Moore, Ilja Preuss, and Bob Worth. I appreciated their suggestions even if Ididn
TWENTY WAYS TO SPLIT STORIES 1. Hardware architects have a “0, 1, infinity” rule – these are the easiest three values to handle. Special cases bring in issues of resource management. 1. Many. It’s usually easiest to get one right and then move to a collection. Split condition. Full condition. Treat “and,” “or,” and “then” and other connector words as100 IMPEDIMENTS
100 Impediments. Posted on August 21, 2009 by Bill Wake. One of the most important things a ScrumMaster does is recognize and remove impediments. This summary sheet includes 100 impediments (PDF) you may run into (though hopefully not all at once:). .MULTI-LEVEL STORIES
Stories Have Multiple Granularities. User stories may seem like they are about specifications but they’re really a lightweight way to explore possibilities. Many teams get too focused on the “card” aspect, using tools to turn user stories into an atomized requirements spec. Instead, we can use stories to think fluidly at multiple levels. INVEST IN GOOD STORIES, AND SMART TASKS As you discuss stories, write cards, and split stories, the INVEST acronym can help remind you of characteristics of good stories. When creating a task plan, applying the SMART acronym can improve yourtasks.
XP RADAR CHART
THE SYSTEM METAPHOR
REVISE TESTS WHILE REFACTORING? IT DEPENDS Some refactorings (e.g., Extract Method or Extract Class) introduce new elements. Should you revise the tests to take these into account? The classic consultant’s answer applies: It depends. LEAN MANUFACTURING AND SOFTWARE SPEECH: METAPHORS FOR EXTREME PROGRAMMING (XP) Test-first, or test-driven development, is one of XP’s fundamental design techniques. It works like this: 1. Write a test, which probably can’t even compile because you haven’t written any real code yet. 2. Implement a stub of the feature, so the test runs but fails. 3.XP ON ONE PAGE
XP on One Page. Posted on February 26, 2002 by Bill Wake. This mini-poster serves as a reminder about most aspects of XP. Poster: XP on One Page (PDF), French. Thanks to Laurent Bossavit, Alex Chaffee, George Dinwiddie, Alan Francis, Ed Hughes, Ron Jeffries, Paul Moore, Ilja Preuss, and Bob Worth. I appreciated their suggestions even if Ididn
TWENTY WAYS TO SPLIT STORIES 1. Hardware architects have a “0, 1, infinity” rule – these are the easiest three values to handle. Special cases bring in issues of resource management. 1. Many. It’s usually easiest to get one right and then move to a collection. Split condition. Full condition. Treat “and,” “or,” and “then” and other connector words as100 IMPEDIMENTS
100 Impediments. Posted on August 21, 2009 by Bill Wake. One of the most important things a ScrumMaster does is recognize and remove impediments. This summary sheet includes 100 impediments (PDF) you may run into (though hopefully not all at once:). .XP RADAR CHART
A Gallery of Team Rooms and Charts – contribute yours! Big Visible Charts (xprogramming.com) – Ron Jeffries. 7+ WAYS TO TRACK USER STORIES use our rate of development to make predictions about what will be done when. understand the evolving “shape” of our product – what it can and can’t do. keep track of who’s doing what. select an “appropriate” amount of work per sprint/iteration. help people coordinate their work. drive a sense of urgency or fear. buildalignment.
EXAMPLES OF USER STORIES 2020 What we have instead is more of a punchlist – a list of tasks to be done. But some of those tasks are user stories as well. Each row has “state” (Keystone, Blocked, Todo, In Progress, or Done) and “who will do what by when”. Most of the things on there are tasks: “Investigate blank screen on first use”, “Set up ad service”. REVISE TESTS WHILE REFACTORING? IT DEPENDS Some refactorings (e.g., Extract Method or Extract Class) introduce new elements. Should you revise the tests to take these into account? The classic consultant’s answer applies: It depends.AUTHORIZATION
Authorization is the process of deciding whether to allow a user can access or use some resource. (Don’t confuse it with authentication, the process of deciding whether a user is who they claim to be.). TDD and Authorization. From a TDD perspective, there are two core tests: that an authorized user can do something, and that an unauthorizeduser cannot.
TWENTY WAYS TO SPLIT STORIES 1. Hardware architects have a “0, 1, infinity” rule – these are the easiest three values to handle. Special cases bring in issues of resource management. 1. Many. It’s usually easiest to get one right and then move to a collection. Split condition. Full condition. Treat “and,” “or,” and “then” and other connector words as NEGOTIABLE STORIES IN THE INVEST MODEL Negotiable stories help even in ambiguous situations; we can work with high-level descriptions early, and build details as we go. By starting with stories at a high level, expanding details as necessary, and leaving room to adjust as we learn more, we can more easily evolve to a solution that balances all our needs.HCI ARCHIVES
Tag Archives: HCI. Don’t Make Me Think: A Common Sense Approach to Web Usability, by Steve Krug. New Riders Press, 2005. This thin book provides guidance on the basics of web usability. It focuses on the importance of doing things in a way Continue reading. Review –MOVIE RETROSPECTIVE
When I'm teaching about retrospectives, there has always been a challenge: a simulated retrospective wants a shared experience. But what shared experience to use? The one experience I know we share is the session we're in, but using a retrospective Continue reading MovieRetrospective→
REVIEW: IT CAN'T HAPPEN HERE Review: It Can’t Happen Here. It Can’t Happen Here, by Sinclair Lewis, 1935. ISBN 0451465644. This story tells how fascism could come to America. Lewis wrote it in 1935 – before Hitler attacked Poland in 1939. It shows that it was not too early to predict the rise and some of the consequences of fascism. I was surprised that bothMULTI-LEVEL STORIES
Stories Have Multiple Granularities. User stories may seem like they are about specifications but they’re really a lightweight way to explore possibilities. Many teams get too focused on the “card” aspect, using tools to turn user stories into an atomized requirements spec. Instead, we can use stories to think fluidly at multiple levels. INVEST IN GOOD STORIES, AND SMART TASKS As you discuss stories, write cards, and split stories, the INVEST acronym can help remind you of characteristics of good stories. When creating a task plan, applying the SMART acronym can improve yourtasks.
XP RADAR CHART
THE SYSTEM METAPHOR
REVISE TESTS WHILE REFACTORING? IT DEPENDS Some refactorings (e.g., Extract Method or Extract Class) introduce new elements. Should you revise the tests to take these into account? The classic consultant’s answer applies: It depends. LEAN MANUFACTURING AND SOFTWARE SPEECH: METAPHORS FOR EXTREME PROGRAMMING (XP) Test-first, or test-driven development, is one of XP’s fundamental design techniques. It works like this: 1. Write a test, which probably can’t even compile because you haven’t written any real code yet. 2. Implement a stub of the feature, so the test runs but fails. 3.XP ON ONE PAGE
XP on One Page. Posted on February 26, 2002 by Bill Wake. This mini-poster serves as a reminder about most aspects of XP. Poster: XP on One Page (PDF), French. Thanks to Laurent Bossavit, Alex Chaffee, George Dinwiddie, Alan Francis, Ed Hughes, Ron Jeffries, Paul Moore, Ilja Preuss, and Bob Worth. I appreciated their suggestions even if Ididn
TWENTY WAYS TO SPLIT STORIES 1. Hardware architects have a “0, 1, infinity” rule – these are the easiest three values to handle. Special cases bring in issues of resource management. 1. Many. It’s usually easiest to get one right and then move to a collection. Split condition. Full condition. Treat “and,” “or,” and “then” and other connector words as100 IMPEDIMENTS
100 Impediments. Posted on August 21, 2009 by Bill Wake. One of the most important things a ScrumMaster does is recognize and remove impediments. This summary sheet includes 100 impediments (PDF) you may run into (though hopefully not all at once:). .MULTI-LEVEL STORIES
Stories Have Multiple Granularities. User stories may seem like they are about specifications but they’re really a lightweight way to explore possibilities. Many teams get too focused on the “card” aspect, using tools to turn user stories into an atomized requirements spec. Instead, we can use stories to think fluidly at multiple levels. INVEST IN GOOD STORIES, AND SMART TASKS As you discuss stories, write cards, and split stories, the INVEST acronym can help remind you of characteristics of good stories. When creating a task plan, applying the SMART acronym can improve yourtasks.
XP RADAR CHART
THE SYSTEM METAPHOR
REVISE TESTS WHILE REFACTORING? IT DEPENDS Some refactorings (e.g., Extract Method or Extract Class) introduce new elements. Should you revise the tests to take these into account? The classic consultant’s answer applies: It depends. LEAN MANUFACTURING AND SOFTWARE SPEECH: METAPHORS FOR EXTREME PROGRAMMING (XP) Test-first, or test-driven development, is one of XP’s fundamental design techniques. It works like this: 1. Write a test, which probably can’t even compile because you haven’t written any real code yet. 2. Implement a stub of the feature, so the test runs but fails. 3.XP ON ONE PAGE
XP on One Page. Posted on February 26, 2002 by Bill Wake. This mini-poster serves as a reminder about most aspects of XP. Poster: XP on One Page (PDF), French. Thanks to Laurent Bossavit, Alex Chaffee, George Dinwiddie, Alan Francis, Ed Hughes, Ron Jeffries, Paul Moore, Ilja Preuss, and Bob Worth. I appreciated their suggestions even if Ididn
TWENTY WAYS TO SPLIT STORIES 1. Hardware architects have a “0, 1, infinity” rule – these are the easiest three values to handle. Special cases bring in issues of resource management. 1. Many. It’s usually easiest to get one right and then move to a collection. Split condition. Full condition. Treat “and,” “or,” and “then” and other connector words as100 IMPEDIMENTS
100 Impediments. Posted on August 21, 2009 by Bill Wake. One of the most important things a ScrumMaster does is recognize and remove impediments. This summary sheet includes 100 impediments (PDF) you may run into (though hopefully not all at once:). .XP RADAR CHART
A Gallery of Team Rooms and Charts – contribute yours! Big Visible Charts (xprogramming.com) – Ron Jeffries. 7+ WAYS TO TRACK USER STORIES use our rate of development to make predictions about what will be done when. understand the evolving “shape” of our product – what it can and can’t do. keep track of who’s doing what. select an “appropriate” amount of work per sprint/iteration. help people coordinate their work. drive a sense of urgency or fear. buildalignment.
EXAMPLES OF USER STORIES 2020 What we have instead is more of a punchlist – a list of tasks to be done. But some of those tasks are user stories as well. Each row has “state” (Keystone, Blocked, Todo, In Progress, or Done) and “who will do what by when”. Most of the things on there are tasks: “Investigate blank screen on first use”, “Set up ad service”. REVISE TESTS WHILE REFACTORING? IT DEPENDS Some refactorings (e.g., Extract Method or Extract Class) introduce new elements. Should you revise the tests to take these into account? The classic consultant’s answer applies: It depends.AUTHORIZATION
Authorization is the process of deciding whether to allow a user can access or use some resource. (Don’t confuse it with authentication, the process of deciding whether a user is who they claim to be.). TDD and Authorization. From a TDD perspective, there are two core tests: that an authorized user can do something, and that an unauthorizeduser cannot.
TWENTY WAYS TO SPLIT STORIES 1. Hardware architects have a “0, 1, infinity” rule – these are the easiest three values to handle. Special cases bring in issues of resource management. 1. Many. It’s usually easiest to get one right and then move to a collection. Split condition. Full condition. Treat “and,” “or,” and “then” and other connector words as NEGOTIABLE STORIES IN THE INVEST MODEL Negotiable stories help even in ambiguous situations; we can work with high-level descriptions early, and build details as we go. By starting with stories at a high level, expanding details as necessary, and leaving room to adjust as we learn more, we can more easily evolve to a solution that balances all our needs.HCI ARCHIVES
Tag Archives: HCI. Don’t Make Me Think: A Common Sense Approach to Web Usability, by Steve Krug. New Riders Press, 2005. This thin book provides guidance on the basics of web usability. It focuses on the importance of doing things in a way Continue reading. Review –MOVIE RETROSPECTIVE
When I'm teaching about retrospectives, there has always been a challenge: a simulated retrospective wants a shared experience. But what shared experience to use? The one experience I know we share is the session we're in, but using a retrospective Continue reading MovieRetrospective→
REVIEW: IT CAN'T HAPPEN HERE Review: It Can’t Happen Here. It Can’t Happen Here, by Sinclair Lewis, 1935. ISBN 0451465644. This story tells how fascism could come to America. Lewis wrote it in 1935 – before Hitler attacked Poland in 1939. It shows that it was not too early to predict the rise and some of the consequences of fascism. I was surprised that bothMULTI-LEVEL STORIES
Stories Have Multiple Granularities. User stories may seem like they are about specifications but they’re really a lightweight way to explore possibilities. Many teams get too focused on the “card” aspect, using tools to turn user stories into an atomized requirements spec. Instead, we can use stories to think fluidly at multiple levels.XP RADAR CHART
INVEST IN GOOD STORIES, AND SMART TASKS As you discuss stories, write cards, and split stories, the INVEST acronym can help remind you of characteristics of good stories. When creating a task plan, applying the SMART acronym can improve yourtasks.
LEAN MANUFACTURING AND SOFTWARETHE SYSTEM METAPHOR
NEGOTIABLE STORIES IN THE INVEST MODEL100 IMPEDIMENTS
100 Impediments. Posted on August 21, 2009 by Bill Wake. One of the most important things a ScrumMaster does is recognize and remove impediments. This summary sheet includes 100 impediments (PDF) you may run into (though hopefully not all at once:). .MOVIE RETROSPECTIVE
When I'm teaching about retrospectives, there has always been a challenge: a simulated retrospective wants a shared experience. But what shared experience to use? The one experience I know we share is the session we're in, but using a retrospective Continue reading MovieRetrospective→
REVIEW: IT CAN'T HAPPEN HERE Review: It Can’t Happen Here. It Can’t Happen Here, by Sinclair Lewis, 1935. ISBN 0451465644. This story tells how fascism could come to America. Lewis wrote it in 1935 – before Hitler attacked Poland in 1939. It shows that it was not too early to predict the rise and some of the consequences of fascism. I was surprised that both THE SOUND OF GREAT FIREWORKS Design Patterns in Java. Design Patterns in C#. Design Patterns Java Workbook. Building Parsers with Java. Steve Metsker Bio : Oozinoz is a fictional fireworks company created by Steve Metsker. Several books use Oozinoz as a setting for examples, including:MULTI-LEVEL STORIES
Stories Have Multiple Granularities. User stories may seem like they are about specifications but they’re really a lightweight way to explore possibilities. Many teams get too focused on the “card” aspect, using tools to turn user stories into an atomized requirements spec. Instead, we can use stories to think fluidly at multiple levels.XP RADAR CHART
INVEST IN GOOD STORIES, AND SMART TASKS As you discuss stories, write cards, and split stories, the INVEST acronym can help remind you of characteristics of good stories. When creating a task plan, applying the SMART acronym can improve yourtasks.
LEAN MANUFACTURING AND SOFTWARETHE SYSTEM METAPHOR
NEGOTIABLE STORIES IN THE INVEST MODEL100 IMPEDIMENTS
100 Impediments. Posted on August 21, 2009 by Bill Wake. One of the most important things a ScrumMaster does is recognize and remove impediments. This summary sheet includes 100 impediments (PDF) you may run into (though hopefully not all at once:). .MOVIE RETROSPECTIVE
When I'm teaching about retrospectives, there has always been a challenge: a simulated retrospective wants a shared experience. But what shared experience to use? The one experience I know we share is the session we're in, but using a retrospective Continue reading MovieRetrospective→
REVIEW: IT CAN'T HAPPEN HERE Review: It Can’t Happen Here. It Can’t Happen Here, by Sinclair Lewis, 1935. ISBN 0451465644. This story tells how fascism could come to America. Lewis wrote it in 1935 – before Hitler attacked Poland in 1939. It shows that it was not too early to predict the rise and some of the consequences of fascism. I was surprised that both THE SOUND OF GREAT FIREWORKS Design Patterns in Java. Design Patterns in C#. Design Patterns Java Workbook. Building Parsers with Java. Steve Metsker Bio : Oozinoz is a fictional fireworks company created by Steve Metsker. Several books use Oozinoz as a setting for examples, including: 7+ WAYS TO TRACK USER STORIES use our rate of development to make predictions about what will be done when. understand the evolving “shape” of our product – what it can and can’t do. keep track of who’s doing what. select an “appropriate” amount of work per sprint/iteration. help people coordinate their work. drive a sense of urgency or fear. buildalignment.
AUTHORIZATION
Authorization is the process of deciding whether to allow a user can access or use some resource. (Don’t confuse it with authentication, the process of deciding whether a user is who they claim to be.). TDD and Authorization. From a TDD perspective, there are two core tests: that an authorized user can do something, and that an unauthorizeduser cannot.
CUSTOMER ARCHIVES
Limiting Beliefs About Evolutionary Design. Posted on May 5, 2021 by Bill Wake. Evolutionary design works by growing a system one capability at a time, keeping the design just sufficient for the system so far. As needs change, the system evolves to meet them. Evolutionary design has its technical challenges, but limiting beliefsContinue reading.
XP ON ONE PAGE
XP on One Page. Posted on February 26, 2002 by Bill Wake. This mini-poster serves as a reminder about most aspects of XP. Poster: XP on One Page (PDF), French. Thanks to Laurent Bossavit, Alex Chaffee, George Dinwiddie, Alan Francis, Ed Hughes, Ron Jeffries, Paul Moore, Ilja Preuss, and Bob Worth. I appreciated their suggestions even if Ididn
NEGOTIABLE STORIES IN THE INVEST MODEL Negotiable stories help even in ambiguous situations; we can work with high-level descriptions early, and build details as we go. By starting with stories at a high level, expanding details as necessary, and leaving room to adjust as we learn more, we can more easily evolve to a solution that balances all our needs. JUMPING THE S CURVE: LIFE EXTENSION FOR PRODUCTS The S Curve. We can transform our picture: instead of looking at “value by value”, add up the values to make a graph of “cumulative value”. That is, rather than points representing the value per story, we “integrate” to get the total value from the first through the nth story. We can look at this curve as having 4zones: Early days
COACH ARCHIVES
Liftoff: Start and Sustain Successful Agile Teams (Review) Liftoff: Start and Sustain Successful Agile Teams, by Diana Larsen and Ainsley Nies. Pragmatic Programmer, 2016. ISBN 978-1680501636. When I visit teams, I often ask them to describe what the project is trying to accomplish, from its sponsors’ viewpoint. Most Continue reading. THE SOUND OF GREAT FIREWORKS Design Patterns in Java. Design Patterns in C#. Design Patterns Java Workbook. Building Parsers with Java. Steve Metsker Bio : Oozinoz is a fictional fireworks company created by Steve Metsker. Several books use Oozinoz as a setting for examples, including:MOVIE RETROSPECTIVE
When I'm teaching about retrospectives, there has always been a challenge: a simulated retrospective wants a shared experience. But what shared experience to use? The one experience I know we share is the session we're in, but using a retrospective Continue reading MovieRetrospective→
CONNECTING STORIES
It lets you authenticate with a card and a PIN, AND. It can tell you the balance of your checking account, AND. It can let you withdraw $20-$100 (in twenties) from checking. We can think of a dozen other features, but we’ll treat these three as the bare minimum: all mustbe present.
MULTI-LEVEL STORIES
Stories Have Multiple Granularities. User stories may seem like they are about specifications but they’re really a lightweight way to explore possibilities. Many teams get too focused on the “card” aspect, using tools to turn user stories into an atomized requirements spec. Instead, we can use stories to think fluidly at multiple levels.XP RADAR CHART
INVEST IN GOOD STORIES, AND SMART TASKS As you discuss stories, write cards, and split stories, the INVEST acronym can help remind you of characteristics of good stories. When creating a task plan, applying the SMART acronym can improve yourtasks.
LEAN MANUFACTURING AND SOFTWARETHE SYSTEM METAPHOR
NEGOTIABLE STORIES IN THE INVEST MODEL100 IMPEDIMENTS
100 Impediments. Posted on August 21, 2009 by Bill Wake. One of the most important things a ScrumMaster does is recognize and remove impediments. This summary sheet includes 100 impediments (PDF) you may run into (though hopefully not all at once:). .MOVIE RETROSPECTIVE
When I'm teaching about retrospectives, there has always been a challenge: a simulated retrospective wants a shared experience. But what shared experience to use? The one experience I know we share is the session we're in, but using a retrospective Continue reading MovieRetrospective→
REVIEW: IT CAN'T HAPPEN HERE Review: It Can’t Happen Here. It Can’t Happen Here, by Sinclair Lewis, 1935. ISBN 0451465644. This story tells how fascism could come to America. Lewis wrote it in 1935 – before Hitler attacked Poland in 1939. It shows that it was not too early to predict the rise and some of the consequences of fascism. I was surprised that both THE SOUND OF GREAT FIREWORKS Design Patterns in Java. Design Patterns in C#. Design Patterns Java Workbook. Building Parsers with Java. Steve Metsker Bio : Oozinoz is a fictional fireworks company created by Steve Metsker. Several books use Oozinoz as a setting for examples, including:MULTI-LEVEL STORIES
Stories Have Multiple Granularities. User stories may seem like they are about specifications but they’re really a lightweight way to explore possibilities. Many teams get too focused on the “card” aspect, using tools to turn user stories into an atomized requirements spec. Instead, we can use stories to think fluidly at multiple levels.XP RADAR CHART
INVEST IN GOOD STORIES, AND SMART TASKS As you discuss stories, write cards, and split stories, the INVEST acronym can help remind you of characteristics of good stories. When creating a task plan, applying the SMART acronym can improve yourtasks.
LEAN MANUFACTURING AND SOFTWARETHE SYSTEM METAPHOR
NEGOTIABLE STORIES IN THE INVEST MODEL100 IMPEDIMENTS
100 Impediments. Posted on August 21, 2009 by Bill Wake. One of the most important things a ScrumMaster does is recognize and remove impediments. This summary sheet includes 100 impediments (PDF) you may run into (though hopefully not all at once:). .MOVIE RETROSPECTIVE
When I'm teaching about retrospectives, there has always been a challenge: a simulated retrospective wants a shared experience. But what shared experience to use? The one experience I know we share is the session we're in, but using a retrospective Continue reading MovieRetrospective→
REVIEW: IT CAN'T HAPPEN HERE Review: It Can’t Happen Here. It Can’t Happen Here, by Sinclair Lewis, 1935. ISBN 0451465644. This story tells how fascism could come to America. Lewis wrote it in 1935 – before Hitler attacked Poland in 1939. It shows that it was not too early to predict the rise and some of the consequences of fascism. I was surprised that both THE SOUND OF GREAT FIREWORKS Design Patterns in Java. Design Patterns in C#. Design Patterns Java Workbook. Building Parsers with Java. Steve Metsker Bio : Oozinoz is a fictional fireworks company created by Steve Metsker. Several books use Oozinoz as a setting for examples, including: 7+ WAYS TO TRACK USER STORIES use our rate of development to make predictions about what will be done when. understand the evolving “shape” of our product – what it can and can’t do. keep track of who’s doing what. select an “appropriate” amount of work per sprint/iteration. help people coordinate their work. drive a sense of urgency or fear. buildalignment.
AUTHORIZATION
Authorization is the process of deciding whether to allow a user can access or use some resource. (Don’t confuse it with authentication, the process of deciding whether a user is who they claim to be.). TDD and Authorization. From a TDD perspective, there are two core tests: that an authorized user can do something, and that an unauthorizeduser cannot.
CUSTOMER ARCHIVES
Limiting Beliefs About Evolutionary Design. Posted on May 5, 2021 by Bill Wake. Evolutionary design works by growing a system one capability at a time, keeping the design just sufficient for the system so far. As needs change, the system evolves to meet them. Evolutionary design has its technical challenges, but limiting beliefsContinue reading.
XP ON ONE PAGE
XP on One Page. Posted on February 26, 2002 by Bill Wake. This mini-poster serves as a reminder about most aspects of XP. Poster: XP on One Page (PDF), French. Thanks to Laurent Bossavit, Alex Chaffee, George Dinwiddie, Alan Francis, Ed Hughes, Ron Jeffries, Paul Moore, Ilja Preuss, and Bob Worth. I appreciated their suggestions even if Ididn
NEGOTIABLE STORIES IN THE INVEST MODEL Negotiable stories help even in ambiguous situations; we can work with high-level descriptions early, and build details as we go. By starting with stories at a high level, expanding details as necessary, and leaving room to adjust as we learn more, we can more easily evolve to a solution that balances all our needs. JUMPING THE S CURVE: LIFE EXTENSION FOR PRODUCTS The S Curve. We can transform our picture: instead of looking at “value by value”, add up the values to make a graph of “cumulative value”. That is, rather than points representing the value per story, we “integrate” to get the total value from the first through the nth story. We can look at this curve as having 4zones: Early days
COACH ARCHIVES
Liftoff: Start and Sustain Successful Agile Teams (Review) Liftoff: Start and Sustain Successful Agile Teams, by Diana Larsen and Ainsley Nies. Pragmatic Programmer, 2016. ISBN 978-1680501636. When I visit teams, I often ask them to describe what the project is trying to accomplish, from its sponsors’ viewpoint. Most Continue reading. THE SOUND OF GREAT FIREWORKS Design Patterns in Java. Design Patterns in C#. Design Patterns Java Workbook. Building Parsers with Java. Steve Metsker Bio : Oozinoz is a fictional fireworks company created by Steve Metsker. Several books use Oozinoz as a setting for examples, including:MOVIE RETROSPECTIVE
When I'm teaching about retrospectives, there has always been a challenge: a simulated retrospective wants a shared experience. But what shared experience to use? The one experience I know we share is the session we're in, but using a retrospective Continue reading MovieRetrospective→
CONNECTING STORIES
It lets you authenticate with a card and a PIN, AND. It can tell you the balance of your checking account, AND. It can let you withdraw $20-$100 (in twenties) from checking. We can think of a dozen other features, but we’ll treat these three as the bare minimum: all mustbe present.
Skip to content
XP123
Exploring Extreme ProgrammingSearch for: Search
Menu
PRIMARY MENU
* Home
* About
EXPLORING EXTREME PROGRAMMING XP (Extreme Programming) is a form of Agile software development. This site contains Bill Wake’s essays on XP, Agile, Lean, Scrum, andrelated topics.
ARE YOU A PRODUCT OWNER OR A WRITER OF USER STORIES? I’D LOVE TO HEAR ABOUT YOUR CHALLENGES AND SUCCESSES AT WILLIAM.WAKE@ACM.ORG!Articles By Role
Customer
Programmer
Tester
Coach
-------------------------Team
MOST POPULAR ARTICLES * INVEST in Good Stories:
I
,
N
,
V ,
E ,
S
,
T
* Resources: Refactoring, TDD
,
Set-Based Design, Coaching, Testing
.
* Twenty Ways to Split Stories* XP on One Page
* Scrum on a Page
* Set-Based Concurrent Engineering * Room and Charts Gallery(Contribute!
Share your pictures.)* Scrum from Hell
* Test-First Challenge * Job Aids (now an external site)* Games (area)
REVIEWS
Check out the reviews (mostly books) on a variety of topics. (Disclaimer: If you buy a book through my link, I get a small creditwith Amazon.)
YOUR HOST
Bill Wake is a senior consultant with Industrial Logic . Check out our great e-learning on TDD, refactoring, user stories, and more! Bill has been involved with XP and Agile software for more than ten years, in a variety of domains including financial, biotechnology, publishing, and more. His other interests include design, games, and dulcimer. Follow Bill Wake on Twitter: @wwake Bill is the author of _Extreme Programming Explored_,
_Refactoring Workbook_, _Design
Patterns in Java_
(with
Steve Metsker), and _Refactoring in Ruby_(with
Kevin Rutherford).
RELATED SITES
Some material formerly on this site has migrated to other sites: * billwake.com contains Bill’s posts unrelated to agile software. * jobaids.info contains material on how tocreate job aids.
Copyright 1994-2018, William C. Wake. All Rights Reserved. PRIMARY SIDEBAR WIDGET AREASearch for: Search
RECENT POSTS
* Connecting Stories * TDD, TCR, and Frequent Commits * Scalable Story Examples * Review: Labyrinths * Review: Parsing Techniques, A Practical Guide (2/e)TAGS
agile analysis
atdd
author
business
charts
classic
coach
computers
conference
cool
customer
design
economics
fiction
games
HCI
history
improv
integration
interesting
intro
Java
job aids
language
lean
learning
metaphor
music
myth
patterns
planning
programmer
refactoring
resources
reviews
scrum
software
spreadsheet
stories
tdd
team
tester
training
XPlorations
ARCHIVES
Archives Select Month November 2019 July 2019 May 2019 March 2019 February 2019 December 2018 November 2018 August 2018 July 2018 June 2018 May 2018 April 2018 March 2018 February 2018 January 2018 December 2017 November 2017 October 2017 September 2017 August 2017 July 2017 June 2017 March 2017 February 2017 January 2017 November 2016 June 2015 May 2015 March 2015 July 2014 January 2014 February 2013 January 2013 September 2012 August 2012 June 2012 February 2012 November 2011 September 2011 August 2011 May 2011 April 2011 March 2011 February 2011 January 2011 October 2010 August 2010 May 2010 April 2010 March 2010 February 2010 January 2010 December 2009 November 2009 October 2009 September 2009 August 2009 July 2009 June 2009 April 2009 March 2009 February 2009 January 2009 February 2008 December 2007 October 2007 June 2007 May 2007 March 2007 January 2007 December 2006 November 2006 October 2006 August 2006 July 2006 May 2006 April 2006 March 2006 February 2006 January 2006 December 2005 November 2005 October 2005 September 2005 August 2005 July 2005 June 2005 May 2005 April 2005 March 2005 February 2005 January 2005 December 2004 November 2004 October 2004 September 2004 August 2004 July 2004 June 2004 May 2004 April 2004 March 2004 February 2004 January 2004 December 2003 November 2003 October 2003 September 2003 August 2003 July 2003 May 2003 April 2003 March 2003 February 2003 January 2003 December 2002 November 2002 September 2002 June 2002 May 2002 March 2002 February 2002 January 2002 December 2001 November 2001 October 2001 May 2001 April 2001 March 2001 January 2001 December 2000 October 2000 September 2000 July 2000 May 2000 April 2000 March 2000 February 2000 January 2000 December 1999 November 1999 July 1999 September 1998 May 1998 January 1998 December 1997 October 1997 September 1997 January 1996 September 1994 December 1992 February 1992 Copyright © 2020 XP123 . All RightsReserved.
Theme: Catch Box by Catch Themes Scroll UpDetails
Copyright © 2024 ArchiveBay.com. All rights reserved. Terms of Use | Privacy Policy | DMCA | 2021 | Feedback | Advertising | RSS 2.0