In my previous post i was talking about retro fitting extreme programming into agile programming… well guess what its been already defined… its called… SCRUM
So what is Scrum development?
It’s a team based, project segmentation development pattern. So whats so new about it nothing really its just a mash up of old and new practices. The project gets split into small segments( or feature for you agile guys) and each team (like in extreme programming) works on a segment.
Since this is basically building developing a project out of small components. The smaller the component the faster you can build the system.
the reason i like this idea is because its an extensible development process.
- Control Chaos: http://www.controlchaos.com/about/]
- Wikipedia: http://en.wikipedia.org/wiki/Scrum_%28development%29
What do i mean by Retro Fitting Extreme Programming Into Agile development?!?!???
Agile Development also known as Feature Driven Development, this is where you build a list of features and the order that they are to be implemented. This responsibility can be placed on the Software Architect or Senior developer.
Extreme Programming also known as Test Driven Development is where you build your test before you code. This responsibility usually is place and should be placed on the Developer and programmers at a slightly Lower level.
I don’t see a reason why these two styles (or methodology) should conflict. You can simply write a set of tests for a feature in your feature list. This should give FDD a bigger success rate.
What happend to the Client ScriptCallback feature of Asp.Net 2.0, Well nothing really happened to Asp.Net 2.0’s client call back…its there and MS Ajax.net (aka atlas) actually uses this in the back end. The reason why we don’t here about it is…it is a paint in the you know what! To actually get anything done….but there was less of a foot print on the page.
Right now we have a couple API’s for writing Ajax is asp.net:
- MS Ajax.Net (aka Atlas)
- Ajax.Net or Professional Ajax.Net
Tips when not to Use Ajax… because the list of when to use it is actually longer…
- If a callback is going to Redirect a user when it get back to the client, just do a post and redirect him or her from there because it gets annoying. If it has to go all the way to server just do a post and redirect or do a Server.transfer.
- Don’t do a call back if it take 30 sec to return, but if you must give the user a message so he or she knows your processing data.
Script Callbacks in ASP.NET