Questioning In groups, the idea is to generate lots of questions about the topic. This helps students focus upon audience as they consider what the reader needs to know. The answers to these questions will form the basis to the composition. Discussion and debate The teacher helps students with topics, helping them develop ideas in a positive and encouraging way.
Some people want to take the stance that no work should be done in advance of the sprint. That is clearly untenable. We were working on an eCommerce site yesterday, but I think maybe we should switch to writing a word processor The start date of the second sprint is knocked forward by the end of the first—like one billiard ball knocking into another.
Having dispensed with the possibility that no work should be done in advance we are left to consider the question of how much work should be done in advance. Many say that as little as possible should be done: My view is that each product backlog item usually reflected as a user story by teams I train or coach should be captured just in time and in just-enough detail for the team to go from product backlog item to working, tested feature within a sprint.
To see why just-in-time and just-enough are appropriate targets, suppose we decide to write a checkbook program to compete with Intuit's Quicken product. We create an initial product backlog that includes these two user stories: As a user I can see the current version, company website, and copyright in a "help about" dialog so that I know useful information about the product.
As a user I can enter a check in my register so that I can track who I pay. That first story can go from that short description to implemented code quite easily within a sprint.
And the programmers will have time to code it and the testers to test it. In short, it meets the just-enough-detail criteria. It encompasses the entire main user interface UI metaphor—will our system look like a paper check register?
How many rows in the register? How will users choose things like check numbers or electronic funds transfer EFT transactions, and so on.
There is no way the UEDs can figure all that out in a two-week sprint. This user story is not explained in just-enough detail. This is where our second attribute comes in: If the team will not work on this user story for six months there is no need to expand on what is already written.
On the other hand, if the team hopes to start it in a few sprints, it is likely time for the UEDs to figure out the answers to the high-level questions listed above. They also agree to spend some time figuring out what the main UI metaphor for the system will be.
During this time the UED may design a couple of screens and show them to a few dozen or hundred users, get feedback, and do it again. This may happen a few times.
When they finish they may have turned that one user story as a user I can enter a check in my register into a dozen smaller stories, perhaps specifying what fields are needed and other details such as: As a user, I can double-click on a check in a list and see the current item look like a paper check.
In some cases splitting a large story into smaller ones is sufficient to show the new items at the right just-enough level of detail.
I like to write user stories on index cards. That was sufficient for the "help about" story. If splitting a story does not add just-enough detail, the UED and others involved may want to staple a UI design spec to the index card. If you are using a software system for managing your product backlog, your virtual staple may be a hyperlink to a wiki page.
The UI design spec that is stapled to the user story card will not yet be perfect; rather it will be close enough that remaining details can be figured out during the sprint.
For example, the UED may not yet have decided if each check should take two rows or three on the screen and wants to do a bit of user testing early in the sprint while the team codes that story. He'll get them an answer early enough that they can do it either way during the sprint.What stages are there in a process approach to writing?
Classroom activities; The importance of feedback; Writing as communication; Potential problems; Further reading What is process writing? The process approach treats all writing as a creative act which .
Marvel's Biggest Baddie Just Wants To Be Your Daddy (Avengers: Infinity War) - Duration: 7 minutes, 29 seconds. Just Write. Just Write. This item has been hidden. Favourite Channels. The Botanical Leaf Kitchen Collection The Botanical Leaf Kitchen Collection is based on one of Michael Aram’s most beloved motifs.
Michael felt that pieces, which are generally left on kitchen counters and tabletops, should be as decorative as they are highly functional.
An introduction to the justice approach to ethics including a discussion of desert, distributive justice, retributive justice, and compensatory justice.
in more traditional terms, giving each person his or her due. Justice and fairness are closely related terms that are often today used interchangeably.
we think it is fair and just when. In any case, a notion of being treated as one deserves is crucial to both justice and fairness. When people differ over what they believe should be given, or when decisions have to be made about how benefits and burdens should be distributed among a group of .
Autoethnography is an approach to research and writing that seeks to describe and systematically analyze personal experience in order to understand cultural experience.
This approach challenges canonical ways of doing research and representing others and treats research as a political, socially-just and socially-conscious act.