Business

Here at LevelTen we have a few book clubs going on. Right now, one of the books we are reading is Agile Estimation and Planning. LevelTen is in the process of implementing an iterative development process which seems to make great sense for small to mid-level Web projects.

Web projects are strange beasts. There are out-of-the-box tools that provide a ton of value. Still small firms with small budgets often have need for custom development that is often prohibitively expensive. The tools to do great things cheaply and quickly just aren't there yet (but progress is being made rapidly).

This entry discuss content type definitions for LevelTen content types.

Answer

During the Knowledge Topic assignment phase, you may be assigned a question to research. The question and answer should be posted to the answer section.

Example:
Question: What is the capital of Massachusetts?
Answer: Boston.

Article

The last blog I wrote was about the nuts and bolts of setting up a contact management database..a real snorer.

I would like to talk today about Intellectual Property. All companies have trade secrets, how your widgets are made, the recipe that goes into your candy, the programing done to develop a piece of software.... Would you let someone walk away with those secrets after working for you for five years? Of course not!

By the late 1990s the Web craze hit the world like Beatle mania. During the Superbowl, the alcoholic beverage industry was overshadowed by dot-com commercials depicting successful e-commerce startups and the idea that everyone could own a successful web business. Someone needed to fulfill the huge influx of web sites that needed to be created and anyone who owned a computer and could learn HTML and create graphics was suddenly a self proclaimed Web expert.

In the Scrum process, the Sprint Retrospective Meeting follows the Sprint review meeting. At this time-boxed 3 hour meeting, the ScrumMaster encourages the Team to revise, within the Scrum process framework and practices, its development processes to make it more effective and enjoyable for the next Sprint.

Further Reading

In the Scrum process, the Sprint Review Meeting is held at the end of each Sprint cycle. It is a 4-hour time boxed meeting at which the Team presents what was developed during the Sprint to the Product Owner and any other stakeholders who want to attend. This informal meeting at which the functionality is presented is intended to bring people together and help them collaboratively determine what the Team should do next.

Further Reading

In the Scrum process, the Sprint Backlog defines the work, or tasks, that a Team defines for turning the Product Backlog into an increment of potentially shippable product functionality.

Tasks should be divided so that each takes roughly 4 to 16 hours to finish. Tasks longer then 4 to 16 hours are merely placeholders for tasks that haven't yet been appropriately defined. Only the Team can change the Sprint Backlog.

Further Reading

In the Scrum process, the Sprint is the name for the process where work is accomplished. A Sprint is a 30-day iteration in which the Team works to complete new functionality from the Product Backlog. Each Sprint is initiated with a Sprint Planning Meeting and ends with a Sprint Review Meeting.

Further Reading

In the Scrum process, the Daily Scrum Meeting is a 15-minute status meeting during a Sprint cycle. Meetings are led by the ScrumMaster.

Purpose:

To synchronize the work of all Team Members daily and to schedule any meetings that the Team needs to forward its progress.

Time & Location:

The Daily Scrum meeting is time-boxed to 15 minutes regardless of the number of Team Members.

Daily Scrum meeting will be held in the same place at the same time every work day - ideally first thing in the morning.

Attendance:

In the Scrum process, the Team is responsible for developing functionality. Teams are self-managing, self-organizing, cross-functional, and they are responsible for figuring out how to turn the Product Backlog into an increment of functionality within an iteration and managing their own work to do so.

Further Reading

Product Owner
ScrumMaster