Part I.

• Iterations must be timeboxed to less than 4 weeks
• Software features must be tested and working at the end of each iteration
• The Iteration must start before specification is complete

Part II.

• You know who the product owner is
• There is a product backlog prioritized by business value
• The product backlog has estimates created by the team
• The team generates burndown charts and knows their velocity
• There are no project managers (or anyone else) disrupting the work of the team

To ensure JSON you’re getting/generating use one of many JSON validators like JSONLint

In HTML 5 elements do not support attributes such as frameborder, scrolling.

The iframe element has three new attributes called sandbox, seamless, and srcdoc which allow for sandboxing content, e.g. blog comments.

New sandbox attribute enables a set of extra restrictions on any content hosted by the iframe.

Possible values:

• allow-same-origin
• allow-forms
• allow-scripts

Seamless attribute allows the inline frame to appear as though it is being rendered as part of the containing document. For example, borders and scrollbars will not appear. This is a boolean attribute. If the attribute is present, its value must either be the empty string or a value that is an ASCII case-insensitive match for the attribute’s canonical name, with no leading or trailing whitespace (i.e. either seamless or seamless=”seamless”).

Possible values:

• [Empty string]
• seamless

Heavy page (around 500k with all scripts and media) with table-based layout:

Same page after refactoring to CSS layout and some bits of JavaScript refactoring:

But there’s seems to be a bug with this feature in Visual Studio 2010 HTML editor. It’s automatically closes the HTML tags you’re typing, but this doesn’t work while editing multiple lines – it’s only closes the last tag which results in broken HTML markup…

1. Table based layout – especially sensitive performance degradation with IE, big number of nested tables also make it look really tricky during the loading time in Firefox and Webkit
2. Superfluous  markup elements – when they are part of repeated elements such as grid or list this results in hundred kilobytes of useless content
3. JavaScript included in the wrong place – this pushes web browser to load/execute JS before you will see the first byte of visible content
4. Lots of HTTP errors, especially 404 and 503 – broken links, moved images, incorrect relative paths to resources
5. Duplicate <link> blocks and JS includes – obvious, but still common problem
6. No caching (content expiration) is set for static resources – both server side caching and content expiration headers for the client
7. Inline <script> blocks
8. GZIP compression is not enabled for CSS and JavaScript files
9. Number of JavaScrip includes for one page – results in big number of network connections, sometimes preventing page to render correctly
10. Incorrect or broken HTML markup – browser spend more time than expected to understand what you were trying to say with <table><div><tr></div><td></tr>/>

- Iteration is a common term in iterative and incremental development (IID).

- Scrum is one specialized flavor of IID.

- Sprint is a scrum specific name for the iteration.

All sprints are iterations but not all iterations are sprints…

As to the sprint length: anything goes as long as the sprint is timeboxed i.e. it is finished on the planned date and not “when it’s ready”. It does help to have the sprints of similar durations.