hasan's blog (বল্গ)

Hi,
thanks for initiating this thread, i will write about my experience on adopting agile.
this is my second company where we are in a transition from waterfall project management to agile based project management.
as you guys can pretend we have so many things to put together to make it easy to understand to those who none believers.

i am very very happy because of the positive and more agile attitude from management bench.
more over management has realized we have to be more picky while choosing client.
fortunately tekSymmetry (our company) is working with those clients who really love us seeing our open collaboration, more friendly attitude and honesty.

our belief is, “we don’t think client as our client we rather think them as our partner” we assist them to get smile on their face at the same time they are helping us to be happy being with them.

to help or accelerate adopting agile we had to do the following stuffs

- after stand up meeting we submitted daily (when sprint is running) “sprint burndown chart” and “sprint backlogs” to the management (management got more curiosity seeing more communication and transparent activities with in the development)

- simplified deployment process, (didn’t setup CI because we wanted more controlled environment, specially i wanted to understand the team and team attitude first)

- initially i had to prepare product backlog to demonstrate how to use it.

- joined with the development team and involved myself in coding

- understanding the development team and management team very closely to figure out how you can be part of their achievement. (thanks to  management because they rather helped me a lot and made so many things easier for us)

- my personal preference is “no give up policy, all human beings are similar possibilities”, i have been working closely and motivating each and every team members.

- helping them to understand they are not away from the standard and smartness.

- initiated “after sprint technical session”, (our talents prepare their presentation and present them to everyone, perhaps someday we will invite audience form many of your companies)

- ran 6 sprints being scrum master, showed them how to manage sprint backlog, how to keep it up to date, available time commitment and daily stand up

- built new scrum master who is now facilitating the core division of the team (we separate the team in two major divisions, core team, new feature team)

- helping him to realize scrum master is not someone who command, rather who “listen and suggest” with soft voice. more preciously he has to eradicate all those blocking issues which interrupting the team.

usually we keep the following stuffs on our scrum

- generally (8 development days, 1 sprint planning and 1 sprint review meeting) = 10 days

- bug fixing sprints are usually 1 week span (4 days work + 2 meeting) = 6 days

- retrospective meeting is organized after sprint review meeting, we used to go for lunch with the team to discuss about “what wasn’t good, could be improved”

- scrum team consists of developers + testers/qa + (soon we will add up designer too)

- test cases are prepared and delivered before any developer take commitment on any feature (though sometimes we can’t get everything before we kick starts coding)

- developer don’t practice test driven development rather they practice “validation driven development” (VDD _))

- i have practiced feature driven release on my previous company

- here we are practicing timely and feature driven release on new company (not yet released anything)

challenge i have faced

- motivating and showing team members their own career path

- helping team to understand the agile way instead of liner way

- making continuous productivity and hyperactivity understandable

- cutting the last moment hero rather making the team as a whole as hero

advantages i have found

- both of the companies where i have introduced agile, (somewhere in… and tekSymmetry) from management perspective view they had agile mindset

- management values human over process

- management is picky about choosing the right client with similar mindset.

btw, feeling constant headache, perhaps that is the reason beyond this
big email _)

best wishes,

this email was sent and published under agilebd (bangladesh agile) group

Recently i had a post in phpexperts group where i wanted to emphasis on managed url. hard coding url is not a good practice besides it ended up with lot of changes on tested code.

Hi,
It has been long while since i last post here in phpexperts group, well i was
away from php for pretty long, being more java and ruby on rails guy when i got
chance to help few php projects, i borrowed few more neat and nifty design
concept from rails to php.

well let me tell you about the story of stories, i ain’t treat myself as php
expert anymore since being detached or keeping my ass out of it. i’d prefer to
call myself as the expert of “work for fun”.

before digging into the details let me explain what was wrong and what could be
wrong with your current way of using URL through out the php application (web
site)

-> Karim, he is given a task to develop a beautiful WOW WOW application in php,

-> He is very WOW WOW developer, develops everything on the fly, produces
(TR/Z/B)*illion of bugs on the fly as well.

-> Very promonient developer, he knows how to write php along html, after
hearing several good advices he started giving CodeIgnitor a shot.

-> So he used to write the following kinda code in everywhere -

<a href=”<?= site_url(“user/profile/10″) ?>”>My profile</a>

Now if you get a chance to look into his view or controller codes, you might see
in everywhere he hard coded the url pattern.

what the hell is the URL Pattern?

well, you see “site_url(“user/profile/10″)” this code is expanded to
“http://abc.com/user/profile/10” while you execute your code in php. this
“user/profile/:number” is called url pattern.

everywhere in his code base he kept such hard coded url pattern.
let’s imagine his client or boss or team lead ask him to change the url pattern
“user/profile/:number” to something similar “profile/:number/”.

now tell me what would YOU DO? if you were placed in such situation?

well you know if that guy was me, i’d run a string replace command through out
the whole project. so wherever i wrote “user/profile/:number” url pattern that
would be converted to “profile/:number”

something like this – /site_url\(“user\/profile\/(\d+)”\)/ replace to
site_url(“profile/$1″)

well i guess many of you already have such problem with similar solution
frankly speaking we had similar problem thus we came up with some solution where
we can change URL pattern without modifying existing view or controller code.

here is the evidence -
<a href=”<?= $this->url->profile(array(“username” => $user_profile->username))
?>”>
<img src=”<?= $this->url->avatar(array(“username” => $user_profile->username))
?>” />
</a>

you see, we ain’t hard coding any url anymore, rather we are calling a function
which are automatically generating from the following kinda configuration -
$urls["profile"] = “http://:username.:host/community“;
$urls["avatar"] = “http://avatar.somewherein.net/avatar/:username/for/aawaj“;
$urls["logout"] = “logout”;

i am pretty sure you guys are smart enough to figure out how we did that, let me
know if you need any help about how we did that.

well first you try yourself and tell me how we did

read the rest of the thread here
you can find out solution here

best wishes,

work for fun!

Welcome to WordPress.com. This is your first post. Edit or delete it and start blogging!