Skip to main content

3 Innovation for our Team

I recently wrote this to propose some changes to our team . I have altered some content to protect our company privacy though.

There 3 major changes that I would like to propose to improve the productivities and competitiveness of the team:
1. Moving to Agile Software Development Methodology
2. Automate and enforce better control in Deployment
3. Speed up Product and User Interface Design & Standard

Both #2 and #3 are crucial for #1.

1. Going Agile
Agile methodology matches our environment greatly where change is unavoidable, shorter product cycle seems to be less risky and frequent inspections on progress and product deliverables are most appropriate.

It can be the greatest evolution for the development team to redeem our reputation of being competitive and productive even as a small team. Also, it will cushion the impediments like poor planning, miscommunication, incomplete design and still-lots-to-be-improved coding.

Followings are the high-level plan for us to go agile:
a) To present the high-level ideas, benefits and execution plan to the management and the team to get buy-in.

b) If receive green light, proceed with more detailed procedures and plans on how to start implementing agile development, most probably co-exist with our old waterfall methodology.

c) Conduct internal trainings for all team members and frequent improvements and changes will happen along the agile adoption. Will also look for opportunities of external training, especially for those in the driver seats.


2. Automate Deployment to QA
It can reduce time and effort greatly to automate the deployment. This is especially necessary when we go agile as the development, deployment and testing iteration are within 1-2 weeks.

It also seems more “urgent” due to the recent support problem in a product where wrong source code is deployed to production and wrong SQL submitted to production while QA copy is correct. Why waste time to troubleshoot and fix the problem when it can be avoidable?

Here are the proposed steps or procedures for automation:
- Nightly update or check out code.
- Nightly build and deploy to QA machine.
- If build failed, send email notification to developers and QA in charge
- Nightly execute checked-in SQLs to QA database.
- Generate daily and weekly CVS report on changes and developers and auto-email to stakeholders and developers.
- Restart QA Application Server every morning to reflect the latest build.

Some sample report will be like this:
http://statcvs.sourceforge.net/statcvs-stats/

3. Speed up Product and UI Design
The current HTML Development to provide the mock-up UI are slow, tedious to make changes and are not able to communicate the page flow, error handling, functional specification effectively to the developers. StpBA Storyboarding is designed to solve this problem. With integration to Visio, it allows for GUI Storyboards, functional specification and test scripts all available at one place. It also able to generate few types of documentations.


A big caveat: Collaboration is an issue as there are different people responsible for functions, test scripts, UI design, etc. So, we may need to explore similar product but with better collaboration to speed up the product design stage.

Another effort will be to embark on an innovation process to redesign the UI to evolve around AJAX technology, hence better usability and simplicity. We can come out of a UI standard with broad knowledge on AJAX technology and research on great usability of other products. Examples will be Basecamp, this blog, etc.

Recently, this blog has implemented Auto-Save Blog Post. I am immensely pleased for this feature. I remembered I used to be in awe when I wanted to save my blog post when I was prompted that I was not connected to the Internet. Then, I waited for the connection to be available and resubmitted my content again. Learning from Microsoft product experience, I even copied out my content before I saved to avoid losing my content if the page hanged or redirected me to some other error pages. If you tried before to submit a long form you have filled to end up losing all the entries when error occured, you will know what I am saying here.


Happy Blogging!
Photo courtesy of http://www.sxc.hu

Comments

Popular posts from this blog

TEAM - Are you a hare, owl, turtle or squirrel?

I just picked up The One Minute Millionaire by Mark Victor Hansen and Robert G. Allen and found it to be very enlightening.

I like the "Multiple Streams of Income" and "Together Everyone Accomplishes Miracles - TEAM" concept.

For team concept, to create wealth - one must first build a diverse team as success is not a solo project. The diverse team consisted of four different categories of workers, known as the Hares, the Owls, the Tortoise, and the Squirrels. Each one has own strengths to leverage on to make the team successful.

Hare - Creative Types, but bad at follow-through.
Owls - Planners and go-getters.
Turtles - Cautious Types who point out issues.
Squirrels - Details oriented person who get the job done.

The one-minute millionaire site offer a survey to determine which type of worker you are. I found out to be a Hare, which I had guessed right. Here is the link to take the survey:

http://www.oneminutemillionaire.com/tools/hots.asp

Below are the explanations of the r…

Myers-Briggs Personality Test

Myers-Briggs Type Indicator which based the test on 16 personality types is popular among big corporation like Coco-Cola. While the cost to take the test is very high, there are several advantages of knowing what type of employees or colleagues you have. Once we know, it is easier to understand others differences in personality , work-styles and learn to deal with the different personalities. Ultimately, the team can work better together.The 16 personality types are derived from the eight basic personality preferences, mainly:Extroversion vs. Introversion
Where do I get my energy? From the external world or people (extroverts), or from data, ideas, or things (introverts).

Sensing vs. Intuitive
How do I perceive information? Sensing types relate to information from their senses (visual, tactile, auditory, etc.) Intuitive types look at the “big” picture – global, spiritual, the possible, the infinite...

Thinking vs. Feeling
How do I make decisions? Through logic (thinking) or through…

21 Irrefutable Laws of Relationship With Your Spouse. Rule No. 4: Law of Bullying Each Other

All of us are definitely no saints, so I guess, there are times we want to be a little bit cruel and act like a spoiled King or Queen.

I supposed most of us cannot behave like King or Queen in the workplace. If not, we risk being fired by our bosses or receive complaints from our colleagues. So, the best person where we can vent our frustration and madness are usually at our other half. Poor thing. Who say love has to be beautiful all the time?

Anyway, as long as we have fun bullying each other, it will be something exciting that we share in the relationship. Caution is - it has to be two-ways. When it is only one-sided, the relationship will stand a chance of being miserable, at least for the person who always get bullied. It also means, if you always get bullied, try to pick up the game and retaliate.

Do note that physical harm or aggressive behaviors are strictly not what I am talking about here. If your partner ever lay a hand on you so much as to cause you pain or small bruises, dum…