13
How Software should get Done Agile software development been around for the last 11 years - only

How software should get done

Embed Size (px)

Citation preview

Page 1: How software should get done

How Software should get Done

Agile software development been around for the last 11 years - only

Page 2: How software should get done

● Software development has been around for a really small period of time as compared to other Engineering sciences

And● that’s exactly the reason why Software

development philosophies Have kept Changing

● All. the. Time.

Times - They're Changing

Page 3: How software should get done

Agile Software?

● Don't Assume Anything - You are NOT the user

● Create - Ship - Observe - Repeat

● Know your game

Page 4: How software should get done

1. I don't usually Assume, but when I do, I don't think I'm the user

● End user behaviour can not be assumed or predicted before they actually end up using the product.

● Everyone is different and is likely to interact with the software in ways we will not be able to foresee.

● Software should be designed with a couple of basic principles in mind:

Page 5: How software should get done

Don't Give the user too Many choices

Page 6: How software should get done
Page 7: How software should get done

Design for Demographics

Page 8: How software should get done

In an effort to make the user feel at home, one must carefully research the target user

Include : demographicspopular cultureand general exposure

so when the users end up using the software, they feel at home.

Page 9: How software should get done
Page 10: How software should get done

Who Am I ?Usman Ahmed"Web Guy", coder, thinker and project manager

Believes software should be: => done by people passionate about what they do

=> with the right technology

Which:=> Get's done correctly=> Is loved by users

Page 11: How software should get done

2 .The software delivery cycle - Create - Ship - Observe - Repeat

a. Create - If the required technical resources are available, use the fastest and most Agile web development frameworks, like Ruby on Rails or django or a similar php framework because developers are able to come up with fully working prototypes in a matter of weeks.

b. Ship - Deploy the product to go live using PaaS such as heroku and appfog

c. Observe - See how users are behaving, which features they’re using more than the others, what buttons the users click on more, what “UX workflows” are the user finding the easiest

d. Repeat - Adjust according to what we found out and ship the software, again.

Page 12: How software should get done

Lay of the Land

Being in the software business means one comes across a bunch of new startups and products every week.

One should keep track of most promising startups and see what they're doing, how they're doing it

what made them fail and what made them succeed.

Based on all of this one should carefully consider their options.

Page 13: How software should get done

People Matter - Because people build, people use and people like or dislike software.

Questions