Microblogging and Specification Document January 22, 2009Posted by simarprit in Microblogging, Uncategorized, websites.
Tags: Agile Development, Agile Software Development, Dil Khol Ke Bol, Microblogging
add a comment
Look, look who’s talking now – Ha! Ha! After all the talk about agile development (AD/ ASD) platform and microblogging, I have finally got down to preparing specifications document. Our Cycle Zero is over, we have made whatever we desired in http://www.DilKholKeBol.com under ASD platform now it is our turn to set our house in order. At this stage we are zeroing down on the right SDLC school/ methodology to be followed to make our microblogging platform a robust multipurpose, easily deploy-able, inherently agile core.
So here we go on what all we have and what all we desire in the Version 3.0 of our microblogging platform.
- We wish to cover 20% of all mobile instruments available in the market. We hope these 20% would be the top 20% in usage thus allowing us to cover 80% market.
- You can do picture upload from mobile through GPRS
- You would be able to video upload through GPRS
- You can do text through GPRS, you would be able to do text through SMS
- Person Search
- Blog Search
- Refresh Indicator
- Uploading from indication
- Seamless integration with blogging site
- Trending topics
- Twitter RSS feed integration
- Picture archiving and Personal/ Public
- Video archiving and Personal/ Pulblic
- Registration features
- Audio integration
- Podcast integration
- Short URL interface
Most of the above is already there, we are going to go ahead and make it to order form made on the fly – what we have done so far.
Please suggest more features…
Agile Web Design September 19, 2008Posted by simarprit in Design, Web 2.0, Web 2.0 Expo, websites.
Tags: Agile Design, Agile Software Development, Software Development Processes, User Experience, Web Design, Web Development
add a comment
Agile Web Design and User Experience in Web 2.0 Environment – Jackson Wilkinson’s session
- Agile web design developments core has to be building a window for failure, and a window for bypassing conventional software development process.
- Agile process has a lot to do with iteration a work cycle approach where you keep on entering and exiting the cycle as you tweak and tune. You handle challenges as you move on. Agile processes are largely collaborative.
- Embedding quality in agile processes brings a better product after each iteration cycle
- Time to do really good design work has no alternative, path of least resistance makes for decidedly inferior products which are likely to be similar to many around
- Cycle Zero must have defined receivables, mood boards or dummies should be handled during cycle zero or phase zero whatever you call it.
- User stories stage and cycle planning is critical to cost and time management
- Collaborative UX meeting and Collaborative UI meetings help in thinking out of the box and get everyone on the same page. Designers get a time to figure how the site is going to look like and what the challenges would be.
- Stand-up stage of just an update and plan for the day helps in monitoring agile development and measuring it over various stages.
- Testing, Validation and Public Demos are parts of the cycle and are looked at at-least once in eavery cycle/ phase
- Be rapid through your cycles and don’t justg et stuck at a point, move on, there are going to be other stages of iteration