So the project looked as follows:

1. Review codebase
2. Review problems with mail delivery
3. Suggest improvements, scope and people needed to bring the project in under budget
4. Do interviews for technical people (ended up interviewing 6 people in a day for 2 roles)
5. Get all code under control, install code revision and management, get developers working on new version of project
6. Implement email fixes to get email into Inboxes
7. Project manage for weekly updates to client

One of the things that made the project manageable from my perspective was hiring the right people from the beginning, so that my work was limited to communication and prioritisation, which is how it should be. My general point of view is that if a product or project manager is spending more than 20% to 30% of their time on any one project, then something is wrong. Maybe 40% on the outside is acceptable for a really technical project, or one heavy in stakeholder communication, but then that’s really becoming an account director or similiar.

So, once the tech people were bedded down and we’d established the priorities for the project, we moved into a nice agile routine which got the project done well under time, making the client happy. Principle lesson and take away – hire the right people from the beginning, and life is easy. Do the opposite, and projects can be hell

So deliverables for this short project were as follows:

1. Review systems and infrastructure
2. Review current search engine optimisation
3. Review site usability and user journeys
4. Deliver document which outlined improvements on all of the above, as well as wireframes for primary layout and pages

The good news is that the client team has been slowly chipping away at the list of suggestions, and they’re starting to make real progress and get search engine results, which is awesome! Take home for me was: persistent, consistent effort is often the only way things get done “in house” as there are often so many competing priorities that the only way to move forward is with a little sculptors hammer – it takes a long time, but you eventually get your masterpiece!

Not doing #agile is like walking thru molasses with your hands behind your back, with blindfolds on, covered in treacle

Note they’re not all the same thing:
Robust is code that doesn’t break, is easily tested, scales well, and where collaboration is easy.
Fast is what it says on the tin, literally releasing new code fast and often.
Agile means being able to change direction, or make changes, quickly.

In my experience, Agile software development is the best way to enable the above – it’s a compromise between speed, collaboration and real results.

So with this engagement, the brief was to review everything (tools, processes, infrastructure, code) and to come up with a document that includes analysis and recommendations. My observation from this experience is that there is a fine line between agile development and chaos, but that this line gets thicker the more you invest in the right systems, processes, tools and infrastructure, which all enable and support doing *stuff* fast.

For example, in no particular order:

1. Testing is harder than it needs to be if there are no testing environments, unit tests, documentation of code, testing scripts, user outcomes (there are many examples, these are just a few)
2. It’s difficult to estimate and prioritise for business priority, when your list of items to work on is not prioritised or you don’t know what dependancies are
3. If you ask people to step outside of their comfort zones, more often than not you’ll be met with resistance. Use tools that make people comfortable
4. If it takes a long time or is difficult, to release a version of your software, then you’ll release less often and make more mistakes
5. If everyone understands the processes involved, you’re more likely to become more efficient. If those processes are changing or non-existent, efficiency is hard to gain.
6. If you’re going in the wrong direction, you don’t want to get there faster. If your code doesn’t support quick changes, you’re not going to be able to change direction quickly

The above are just some examples that were pertininent, so you should get the general idea.

My hope is that with the right motivation, we’ll fix the issues holding things back by setting up the right infrastructure and processes to support the business goals, and end up creating an environment that does indeed foster robust, fast, agile development.

We also need the following:

1. Allow emails from more than one account to be diverted to the system and converted into tickets which can be assigned to team members according to language.
2. Have predefined responses stored in a database which can easily be included as a basis for an email
3. Allow specific emails from specific accounts to be automatically assigned to individuals
4. Have various levels of importance for support requests
5. Should allow the creation of different groups with various role capabilities

If you have any suggestions or experience to share please let me know in the comments.

Update: we’re using eSupport

Check it out, you should start to see the first signs of our social direction, which sets us apart from being “yet another genealogy application”… 11 Languages helps too…

_ Kindo – Some new features & improvements to kindo

The kindo team is very proud to announce that we have released a number of new features which we hope will improve our users’ experience.

Firstly, we have added 3 new languages, namely Russian, Turkish & Brazilian Portuguese, which now brings the tally to 11.

Our family

Secondly, we have added a brand new page called “Our family”, where you can view the latest updates from all of your active family members. It also has a section with family statistics, so you will be able to see some interesting facts about your tree – the more data the better, so start updating those profiles

From:
http://blog.kindo.com/

We have also released a new blog on blog.kindo.com, so if you would like to keep up to date with our latest news, then please visit it. Comments are more than welcome

Here are some snippets from two interesting posts on the Kindo blog

http://blog.kindo.com/2007/08/02/some-technical-details/en/

We’re having fun building the Kindo application and used a number of frameworks and components to achieve the finished result.

For the web framework we’re using Seagull which offers excellent integration with Flash through the AMF PHP request handling and easy integration with Ajax and Graphviz. For the Ajax interactions we use jquery exclusively, for Graphviz a heavily extended version of the PEAR lib of the same name. Working with the dot language has been interesting and a good opportunity to experiment with the subtleties of a genealogy graph.

http://blog.kindo.com/2007/09/04/welcome-to-the-beta-release/en/

A little while ago we released an Alpha to a small group of people, to gather valuable user feedback. Thanks to those great people, we’ve had our heads down improving Kindo, and as a result we’re releasing the Beta, and at the same time opening it up to a wider audience for more feedback.

I recently installed the Vanilla forum and set it up so that it would not allow public browsing, because the discussions there are top secret

I then installed the Feedpublisher extension to allow for RSS2 and ATOM feeds.

Problem

I encountered a major problem though, the rss feeds were not accessible because the forum did not allow public browsing. I also saw that on the vanilla community forum, this problem had been rasied, but no-one had offered a solution.
Also, when trying to access the feed through the browser, one gets an authentication pop up box requested a username and password. When one enters the username and password into the respective text fields the following error message is displayed:

A fatal, non-recoverable error has occurred
Technical information (for support personel):

The error occurred on or near: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '(u.Password = md5('foobar') or u.Password = 'foobar' )' at line 1


Solution

After quite a bit of playing around and testing, I found a relatively easy solution to the problem – typical a five minute fix for an error that keeps you busy for 2 hours!!!

Step 1


So firstly go to /extensions/Feedpublisher/default.php and make sure that the following section of code looks like this (line 60-73 )

}

Step 2

Then login to the admin section of the forum go to settings > categories > $category edit

Then you need to check the “unauthenticated” option in the “Roles” and hot save. Do this for each and every category, unless you don’t want a specific category to be displayed on the feed.

This method fixed my problem, so I would be interested to find out if anyone else has a better solution. Also let me know id it doesn’t work for you – I hope that’s not the case though.

The site which I am talking about is http://bd4d.com, which stands for By Designers 4 Designers is built using the seagull php framework with the new cms module

General comments

Media Temple Installation

During the live installation I encountered a few problems, most of which related to permissions of files on the server:

The main one however were the permissions of the /var/lib/php/session/ folder – it has to be writable

Plugins that I found really useful during development

There were two firefox plug-ins that I found very useful during development of the site:

Colorzilla – gives you # codes for colours on any webpage
IE tab – allows you to open up ie7 tabs within firefox, which is great for cross browser compliant xhtml/css

Thanks to the developers of these two add-ons

Paypal

The site has a payment gateway for listing jobs and events which has transaction processing done by Paypal.

In terms of project mistakes, this was one of the biggest we made. The support that James received from Paypal was extremely poor and the general documentation which they supply is often out of date and incorrect. I am amazed that they have become such a successful company, when it is so difficult to integrate their transaction processing into one’s site.

However after a lot of waiting for accounts to go live, numerous queries, emails, phone calls and a lot of frustration, we did eventually get the transactions working. It is working fine now, but it was definitely not worth all of that hassle.

I would be interested to here about other experiences from developers using Paypal – hopefully you had a better one than we did.

Site Features

Showcase

The section of the site that I am most proud of is the Showcase section, which has flash and movies of some really cool clips which the bd4d guys have done. The section allows comments to be made on each of the movies and I think it looks pretty slick – even if I say so myself

To get the section functioning, I used the following:

A comment manager which Dmitri initially developed and then I adapted that code to be used for the site.

To prevent spam on the site I used captcha package from the php pear library

And I used the following code in the template to hold the movies/flash files:

< object width="550" height="400" >
< param name="movie" value="{webRoot}/themes/bd4d/showcasemovies/
{oItem.media}" >
< param name="quality" value="high" >
< embed src="{webRoot}/themes/bd4d/showcasemovies/
{oItem.media}" quality="high" width="{oItem.width}" height="{oItem.height}" autostart="true">< / embed >
< / object >

Events

The Events calendar uses the default seagull events module as a basis, but there where a few enhancements made to fit the requirements of the site. The majority of the development of this section was done by James and I think that he did a pretty good job of it.

The calendar looks pretty slick and works really well, also the backend of the seagull events module provides a lot of flexibility for administrators wanting to manage events.

Job board

The Job board uses custom managers in the default module and as I have mentioned in my section about paypal, it allows members of the site to post jobs for a fee. The transaction processing handles straight paypal payments as well as credit card payments which are verified by paypal.

Conclusion

As I mentioned in the introduction this site took way longer than expected and there were a number of hard lessons which the whole team learnt. But at the end of the day, the site looks pretty good and works as expected, so in some way it can be seen as a success.

I used to just leave the .ico file in the document root and hoped that the browser would pick it up, but I have recently been told a much better way of ensuring that the correct image is displayed in the URL text field.

Place the file in the images folder and then refer to it in your the head of you html template by using the following code: < link rel="Shortcut Icon" type="image/x-icon" href="../images/favicon.ico" / > (remove spaces in code)

So, one definitely does learn something new everyday. Hat tip to Ali