Lara Kannan

Start doing daily stand up meeting in Agile programming method

A daily standup meeting is one of the easiest practices you can implement with your team. It only takes 10-15 minutes at the beginning of each day, and it increases the amount of communication and synchronization in the team immensely.

The idea is very simple...

The whole team (usually no more than 10 people) literally stands up in a sort of circle so everyone can see each other. then the team lead (or the "facilitator" that was chosen for the team) will go one by one and ask each team member three simple questions:

1. What did you do yesterday?
2. What are you going to do today?
3. Is there anything stopping you from getting your work done?

Question #1 is important for several reasons:

• Everyone hears what happened yesterday and know the current status on that part of the app that member worked on


• The team lead understands the progress of the team member and the overall status of the app


• If the team member didn't get anything really done yesterday, it might mean they are stuck - which is very important to know early as we've seen.

Question #2 also has its uses:

• The team member stands up in front of their own peers and says they will do something. They will feel more responsibility to make sure those things get accomplished. they are now accountable to the team.


• If they do not know what to do today, that's also good since you've caught this early. make sure they know what to do. If there is a task board, they can grab the task with the highest priority, for example.


• Other team members will know what is going on, can offer help or tips (maybe they worked on this just the other day?)

Question #3 is very important to prevent bottlenecks in the team productivity

• maybe someone's computer is overheating, or has low memory


• maybe a team member needs to take half a day since some other project called them


• maybe... you get the idea

it is your job as a team lead to make sure nothing is stopping team members from working on the things with the highest value to the project(s) they are working on. If they are not, find out why and solve it immediately after the meeting.

5 useful tips I learned the hard way

1. Make sure it does not take longer than 15 minutes (that's why standing up is important - people don't feel comfortable ranting on when they stand up so things finish up quickly)


2. Make sure that technical discussions do not ensue in the middle of the meeting. when one breaks out call it out as a "talk about this later, just the both of you" and ask people to move on


3. When all else fails, you can tell the person who won't stop talking - "you have 30 seconds to finish your overview" and then move on.


4. Don't be afraid to stop people in the middle of speaking. The rules must be clear and concise.


5. Once you have this meeting, try to see what meetings you can now cancelfor the whole team. For example, in our company we have only two meetings a week where the whole dev team needs to be in: daily standup, and once a week a company meeting. besides those they are just at work, working.

Thanks :5whys.com

Happy Programming!!!

Share your thoughts with me !!! A 'Thank You' would be nice!

Most people would agree the default look of submit buttons is rather dull and unattractive. Using CSS and a nice gradient background image, it's easy to transform a form button from a duck to a swan.

Demo:

<style type="text/css">
.formbutton{
cursor:pointer;
border:outset 1px #ccc;
background:#999;
color:#666;
font-weight:bold;
padding: 1px 2px;
background:url(formbg.gif) repeat-x left top;
}
</style>
The image used:

<form>
<input type="text" style="width: 200px; border: 1px solid gray" />
 <input type="submit" class="formbutton" value="Submit" />
</form>

I hope this ll help you. A 'Thank You' would be nice!

A nice feature of CSS is the ability to assign multiple classes to can DOM element via the class attribute. This opens up the possibility to dynamically set a class assignment based on some logic as the page is being rendered.

The example below demonstrates having a common style rule and a rule added at run-time. Of course you are not limited to this methodology, there are many ways to apply styles to an element.

<div class="contentBox bkg1">...</div>

I find the solution from Chris blog, for easiest way to set something like a dynamic style at run-time is to define a public method in the page class to return the desired rule. For my demonstration I will return a style rule name based on a QueryString parameter, but you can use all sorts of criteria. I also chose to apply the rule to the Body tag.

This is a simple method to return a style rule to define the background color of the page. I have three rules defined.

public string GetBackgroundClass()
{
    switch ( Request.QueryString["bkg"])
    {
        case "1":
            return "bkg1";
        case "2":
            return "bkg2";
        case "3":
            return "bkg3";
        default:
            return "bkg1";
    }
}

The style rules just set the color as follows, a nice egg shell (at least that is what I call it), red and blue.

.bkg1
{
    background-color: #FFFFCC;
}

.bkg2
{
    background-color: #C30000;
}

.bkg3
{
    background-color: #0000CC;
}

Finally I just inline the call to the method in the HTML markup:

<body class="<%=GetBackgroundClass() %>">

I hope this ll help you. A 'Thank You' would be nice!