. Thank you for visiting Width Requirement To Display InFrame Infolinks
Showing posts with label General. Show all posts
Showing posts with label General. Show all posts
Sunday, 10 February 2013
Width Requirement To Display InFrame Infolinks
. Thank you for visiting Width Requirement To Display InFrame Infolinks
Monday, 16 April 2012
Most Funny Facebook Status Update
People with Problems
- You asked the cop if you could use his in-car computer to update your Facebook. No way you were getting out of a DUI.
- The most awkward part of meeting new people is when my kids say, “Please help us.”
- I drank so much Goldschläger last night, I could shit a necklace.
- If at first you don’t succeed, try drinking beer while you do it. You’ll be amazed at how much less you care.
- He let me duct tape his mouth because I said it was my fetish; I really just wanted him to shut up.
For Halloween
- Eat, drink and be scary.
- I am dying to have a great Halloween with you.
- … wants to remind you this Halloween, that as a general rule, don’t solve riddles that open portals to Hell.
- … wonders if he’s getting old, or if others also ask for high-fiber candy only on Halloween?
- … thinks that cauldron of Halloween candy has been undressing me with its eyes from across the room all night…come here you.
For the New Year
- I will stop using FB as a tool of procrastination and actually do some homework.
- I will avoid taking a bath whenever possible and conserve more water.
- I resolve to work with neglected children. (my own).
- I will stop judging myself on how many people I have on my friends list. Also, stop taking posed, extreme angle profile pics…if you know me you know what I really look like!
- I will try to find a way to politely lose the 4 most annoying Facebook friends.
For Uninspired Times
- Insert coin to view status message.
- If you have a parrot and you don’t teach it to say,”Help, they’ve turned me into a parrot”, you are wasting everybody’s time.
- The obscure we see eventually. The completely obvious, it seems, takes longer.
- When I was born I was so surprised, I didn’t talk for a year and a half.
- … is cle’a[ni.ng hi's ke]yb36oa;rd
Thursday, 19 January 2012
Easy WordPress to Blogger Converter ( Software to Convert Worpress xml to Blogger xml )
This software can Convert Worpress xml to Blogger xml. Just open the rar file and click the Program.exe. Thank you for visiting Easy WordPress to Blogger Converter ( Software to Convert Worpress xml to Blogger xml )
Saturday, 30 April 2011
Writing Good User Stories
User Stories are a simple way of capturing user requirements throughout a project – an alternative to writing lengthy requirements specifications all up-front.
As a guide for people writing User Stories, they can follow this basic construct:
As a [user role], I want to [goal], so I can [reason].
This helps to ensure that the requirement is captured at a high level, is feature oriented and covers who, what and why.
As well as capturing User Stories in the above format on the Product Backlog, User Stories should be written on a card.
The card comprises 3 parts:
Card (i.e. the bit above, “as a user, I want…”)
Conversation (notes and/or small wireframe to remind people about the feature)
Confirmation (the tests that will show the feature is complete)
Here’s an example User Story for you to take a look at.
Ultimately, User Stories should be small. But when they’re first entered on the Product Backlog, when they’re quite a way from being developed, they can start out large and fuzzy. While they are in this state, they are known as Epics.
Software requirements are a communication problem. There is no perfect solution. User Stories seek to find a balance between written and verbal requirements, relying on collaboration between team members to clarify details near the time of development.
Here’s a PowerPoint presentation about User Stories to help share the concept with others.
The INVEST acronym can help you to remember and assess what makes a good User Story. User Stories should be:
* Independent. Okay, for some systems, it’s near impossible to make each feature completely independent. In other solutions, e.g. web sites, it’s easier. But it’s an important aspiration. User Stories should be as independent as possible.
* Negotiable. User Stories are not a contract. They are not detailed specifications. They are reminders of features for the team to discuss and collaborate to clarify the details near the time of development.
* Valuable. User Stories should be valuable to the user (or owner) of the solution. They should be written in user language. They should be features, not tasks.
* Estimable. User Stories need to be possible to estimate. They need to provide enough information to estimate, without being too detailed.
* Small. User Stories should be small. Not too small. But not too big!
* Testable. User Stories need to be worded in a way that is testable, i.e. not too subjective and to provide clear details of how the User Story will be tested.
I hope this series of posts has been useful. If you want to browse through all these posts about User Stories, you can do so here: Writing good User Stories.. Thank you for visiting Writing Good User Stories
10 Key Principles of Agile Development
10 Key Principles of Agile...
Agile Principle 1: Active User Involvement Is Imperative
In my mind, active user involvement is the first principle of agile development. It's not always possible to have users directly involved in development projects, particularly if...
Agile Principle 2: Agile Development Teams Must Be Empowered
An agile development team must include all the necessary team members to make decisions, and make them on a timely basis. Active user involvement is one of the key principles to...
Agile Principle 3: Time Waits For No Man!
In agile development, requirements evolve, but timescales are fixed. This is in stark contrast to a traditional development project, where one of the earliest goals is to capture...
Agile Principle 4: Agile Requirements Are Barely Sufficient
Agile development teams capture requirements at a high level and on a piecemeal basis, just-in-time for each feature to be developed. Agile requirements are ideally visual and should...
Agile Principle 5: How Do You Eat An Elephant?
How do you eat an elephant? One bite at a time! Likewise, agile development projects are delivered in small bite-sized pieces, delivering small, incremental *releases* and iterating. In...
Agile Principle 6: Fast But Not So Furious
Agile development is all about frequent delivery of products. In a truly agile world, gone are the days of the 12 month project. In an agile world, a 3-6 month project is strategic! Nowhere...
Agile Principle 7: Done Means DONE!
In agile development, "done" should really mean "DONE!". Features developed within an iteration (Sprint in Scrum), should be 100% complete by the end of the Sprint. Too often...
Agile Principle 8: Enough Is Enough!
Pareto's law is more commonly known as the 80/20 rule. The theory is about the law of distribution and how many things have a similar distribution curve. This means that *typically*...
Agile Principle 9: Agile Testing Is Not For Dummies!In agile development, testing is integrated throughout the lifecycle; testing the software continuously throughout its development. Agile development does not have a separate test..
Agile Principle 10: No Place For Snipers!
Agile development relies on close cooperation and collaboration between all team members and stakeholders. Agile development principles include keeping requirements and documentation.... Thank you for visiting 10 Key Principles of Agile Development
How To Implement Scrum in 10 Easy Steps
There’s a myriad of different approaches, principles, methods and terms, all of which are characterised as ‘Agile’. And from my perspective, all this ‘noise’ makes agile software development sound far harder, far more scientific, and far more confusing than it really needs to be.
For this reason, I favour the Scrum agile methodology. Admittedly there’s a bit of jargon to learn. But otherwise Scrum provides what is fundamentally a very simple way of managing software development more effectively.
Sure, it’s great to have a deep understanding of the underlying values and principles of agile development.
Sure, it’s great to have a thorough understanding of why Scrum works.
Sure, it’s great to know lots of case studies where Scrum has been applied and try to relate them to your own individual situation.
But, fundamentally, I believe you can implement Scrum without all this knowledge. And still find many benefits and have a very positive experience of agile development.
In these 10 posts, I outline specifically how to implement Scrum in 10 easy steps:
- Step #1: Get your backlog in order!
- Step #2: How to estimate your product backlog
- Step #3: Sprint Planning/clarify requirements
- Step #4: Sprint Planning/estimate tasks
- Step #5: Create a collaborative workspace
- Step #6: Sprint!
- Step #7: Stand up and be counted!
- Step #8: Track progress with a daily burndown chart
- Step #9: Finish when you said you would
- Step #10: Review, reflect, repeat…. Thank you for visiting How To Implement Scrum in 10 Easy Steps
Friday, 29 April 2011
Prince William & Kate Middleton Wedding Pictures
It's the moment the whole world has been waiting for – The Royal Wedding of Prince William and Kate Middleton is scheduled to take place at Westminster Abbey on today (29 April 2011) at 11am. It is destined to be a global media event. People around the globe are clamoring to see what the bride-to-be will wear, how the ceremony will go down, and what the future will look like for these two icons. Britain hasn't seen a royal wedding of this size since William's father Prince Charles married the late Lady Diana Spencer in 1981.
Thousands of well wishers have lined the mile-and-a-half route to Westminster Abbey to celebrate the marriage of Prince William today. Kate and William both enrolled at St. Andrew's College in Scotland and graduates together from St. Andrew's -- William with a Master's in Geography (and second honors), Kate with a Master's in History of Art. More than 2,000 guests are expected to attend the ceremony including royals, heads of state, celebrities and charity representatives. There were actually 200 more police on duty for that wedding, which had a longer procession route and a guest list of some 3,500 people, including foreign royals and heads of state.
The wedding is scheduled to begin at 15:00 pm IST and The event will be aired live on NBC, CNN, DISH, BBC, and other networks at 1 AM PT/4 AM ET. Checkout here Prince William Kate Middleton Wedding Ceremony Photos, Prince William Kate Middleton Wedding Ceremony pictures, Prince William Kate Middleton Wedding Ceremony wallpapers, Prince William Kate Middleton Wedding pics, Kate Middleton & Prince William Westminster Abbey Photos, Pics & Images.
Prince William & Kate Middleton Royal Wedding Photos & Pictures
. Thank you for visiting Prince William & Kate Middleton Wedding Pictures
Subscribe to:
Posts (Atom)