We need a Project Manager at Simpleweb HQ

by Simpleweb Filed under: Company

We’re growing and to keep projects streamlined we’re looking for a project manager. If this is you please send your cover email and CV to Holly. If  you know someone please let them know and if they’re successful we’ll give you £200.

Here’s the official description:

Simpleweb is a small, fast-paced and energetic company with big ambitions, great ideas and a focus on building awesome web based products. We have an agile approach to development and are looking for a talented, dynamic and organised Project Manager with a track record of delivering digital software applications to join our brilliant team.

We are looking for a driven and focused Project Manager who can handle multiple projects easily, isn’t phased by abnormal working hours and takes pride in their results.

You will be core to our greatest asset – our team, a hard working, creative team of developers who like to play hard too…

We build everything from simple WordPress sites, web start-ups to our own products. You will already have a broad range of experience that you can bring to every project.

Personal Traits:

You will be a pragmatic and outgoing person with a passion for online projects and not shy away from the challenge of effectively and confidently managing a range of projects.

You need to be a great team player, love technology, have entrepreneurial spirit, with a good sense of humour, a bucket load of common sense and enjoy delivering great results.

Responsibilities:

● You will be responsible for the delivery of simultaneous projects to a high quality, on time and on budget through the effective management of clients, people and resources.

● The Project Manager is the first point of contact for clients so is responsible for managing expectations, problem solving and elevating issues at the appropriate times.

● Provide the team with clear insight into project requirements and expectations highlighting critical success and failure points.

● Work with technical team to determine feasibility of possible solutions and assist in decision making based on project expectations, time and cost.

● Manage our internal projects with a consistent approach to our client work.

● Effectively manage time and resources for ongoing client support for issues that arise outside of fixed projects, in line with our SLAs.

● Run suitable project debriefing sessions and work with directors to assess where ongoing improvements to processes can be made.

Remuneration:

● Salary competitive depending on experience

● Company share options

● Private medical insurance

● Pension scheme

To apply, please send us a cover letter/email with a bit about yourself and a concise CV outlining your experience to Holly

No agencies please.

Optimisation Tactics

by adambutler Filed under: Knowledge,Optimisation

Optimisation is a core element in building any successful product regardless of whether its a website, an app or even a game. But optimisation isn’t just about keeping the file size down its about providing the most fitting possible solution for any given task.

When optimising we think about value, usability, readability, communication and personality as well as the more traditional foundations such as SEO and load times. Covering all these core concepts will ensure you have a delicious product.

So how do we do it?

Throughout each step of design, development and testing we think about these core principles based on our collective experience and through experimenting. Here is one such example…

For one of our top secret projects we have in development we have two large containers which you can navigate between, we found that having a drop shadow these containers caused a subtle but noticeable lag when animating in and out. As with any project there is always more than one technical way to active a task so we brainstormed potential fixes which would allow us to keep the design with a drop shadow.

We decided to trial our current method (A), animating css position values, against CSS Transitions (B). To stress test the demo each container was filled with 2312 child elements all individually coloured and with opacity. The parent containers have the same drop shadow as we intend to use in our project.

Method B out performed A quite significantly in each of the tests. Spending just a little bit of time on this problem helped ensure we had a buttery smooth animation. Although this is a very specific example this logic is used each of the optimisation tests that we run and is essential to making great products.

You can view this test here…. but remember it is a stress test so it may crash your browser.

We’re giving away 5 free websites

by Mark P. Filed under: Case studies,Community,Company

We’ll build you a “support based application” to compliment your existing website. We’ll design it, set it up and host it for you. All you need to do is tell your customers!

Why are we offering these for free? Well, we want to build up some great case studies demonstrating social interaction and “customer listening”. We’ve got five to give away and we’ll let you know by the middle of April if you’re eligible.

There are two types of support applications that we’re offering to build for you:

Customer Voice

Allow your customers to ask questions, suggest ideas and discuss other peoples ideas. Your customers sign in quickly with Facebook or Twitter and can then add a new idea, question, comment or vote up somebody else’s idea or question. View by most recent, popular or just your submissions.

Great for product discussion, quick customer feedback, FAQ’s, etc.

Customer Forum

A traditional looking customer forum deeply integrated with Facebook and Twitter. You and your customers can start discussions about specific topics quickly and with just a few clicks. Presented simply for non technical users making it as easy as possible for you and them to interact around specific topics.

Great for in-depth discussion about any topic.

Both products offer tight integration with Facebook and Twitter, a design that fits your current website and integration with your current mailing system.

[If you can see the form below please try this link instead]

Changing our Git Workflow

by Tom H. Filed under: Knowledge,Technology

We’ve been using Git for quite a while now. We don’t have a single SVN repository. This makes for happy developers!

For a while we’ve been using Git Flow as our preferred workflow. It’s been pretty good, certainly from the point of having some sort of a recognised workflow/process. The only problem is, it’s turned out to be a bit heavyweight for what we want.

We love agile development, and for us, this means:

  • Short sprints of development
  • Regular releases (minimising serious issues)
  • Flexibility to experiment and throw away bad ideas
  • Team spirit and collaboration

The problem with git flow is it’s far better suited to a fairly fixed release cycle. We’ve found the release mechanism is cumbersome for quick/regular releases, and… it’s all a bit heavyweight for the entire team. We want all of our team to feel they can commit and contribute without feeling they might break something in the process. We also want to encourage communication, collaboration and experimentation!

So, the solution is, we’ve switched to Github Flow way of working. So what is it? The basic principles are this (stolen from http://scottchacon.com/2011/08/31/github-flow.html):

  • Anything in the master branch is deployable
  • To work on something new, create a descriptively named branch off of master (ie: new-oauth2-scopes)
  • Commit to that branch locally and regularly push your work to the same named branch on the server
  • When you need feedback or help, or you think the branch is ready for merging, open a pull request
  • After someone else has reviewed and signed off on the feature, you can merge it into master
  • Once it is merged and pushed to ‘master’, you can and should deploy immediately

Here’s an excellent presentation that explains it:

What about clients reviewing code before it might be production ready? Well, we simply push a given feature branch to our stage server. If two developers are working on a separate feature branch, they can either merge each other’s feature branches or create a new shared branch for the purpose of a client reviewing code.

We’ve dropped all our develop branches and the team have been merrily discussing pull requests and getting stuff done. So far so good, we are liking the shift a lot.

User stories, luvvies and conveying project scope

by Mark P. Filed under: Knowledge

We get sent a lot of ideas for apps; mobile and web based. Sometimes we get the most amazingly detailed documents that give us a thorough understanding of what the idea is and what it’s supposed to achieve.

Inevitably this is the exception to the rule, as being from different industries most people know what  they want yet find it difficult to know the best way to describe it and miss out large chunks that are important to us. In the NLP world this is known as “deletion”. We all do it; “pass me that”, we delete the reference assuming that whoever we are talking to knows what we’re on about.

When we get job referrals like this, at the expense of possibly losing the project we ask the potential client to clarify their idea with two specific processes. This also helps us determine if they are serious about the project.

  1. What’s the essence of the idea? This is essentially the elevator pitch.
  2. User stories. What platforms and users are involved and what can they do. We call this the “stage” and actors.

The five minute elevator pitch

Distilling the essence of an idea into a single sentence is a really great way to communicate your project succinctly. A nice template to get this up and running quickly is as follows:

  • For [target customer]
  • who [statement of need or opportunity]
  • the [product name]
  • is a [product category]
  • that [key benefit, compelling reason to buy].
  • Unlike [primary competitive alternative]
  • our product [statement of primary differentiation].
As an example for ContactZilla
For teams and businesses who need to keep track of their contacts the ContactZilla platform is a contact management solution that is completely social. Unlike Sugar CRM our product merges contacts from social media and traditional sources effortlessly.

Just this one statement helps with our understanding in a really big way. It’s quite a fun exercise too. We originally discovered this in the book “The Agile Samurai“.

User Stories

User stories are a pragmatic way to get a project communicated effectively. Essentially you are describing what the application should do for particular types of user and while not telling the developer how to do it. This means you don’t have to keep asking “is it possible?” you just state what is needed. The developer then needs to figure out how; with the resources available.

Project managers will weep that we ask a prospective client to come up with user stories. It is such a simple way to convey interactions, goals and functionality that even if done badly it’s usually more helpful… (we can argue about that in the comments)

First you need to identify the “stage”, this is a simple theatre metaphor that a lot of people understand straight away – the stages in a lot of cases can be an administrative area and a public facing area. We then need to identify the “actors”. These are the different types of luvvie people interacting on your stages. For example an administrator, a guest visitor, a bronze user, etc. This then leads to the user stories themselves.

As an [actor], I can [feature] so that [reason]

As an Administrator, I can delete a blog post so that I can keep things tidy.

You may find that you don’t need the reason, so get rid of it.

As an Administrator, I can delete a blog post.

If we now combine this with the stages we can break up the user stories into sections;

Administration Area – Managing Users

As an Administrator I can delete a user

As an Administrator I can send a message to a user

My profile page

As a logged in user I can update my profile picture

As a logged in user I can change my biography

You can take this much further as a project manager and a development team but for the sake of simplicity this gives a client a really good starting point to convey what they want to achieve in a succinct format.

We find that most clients find this a really rewarding process, it focuses them on what they want to achieve as opposed to how to achieve it. In some cases it also demonstrates the complexity of what it is they want and either validates or invalidates their idea. Which we can all agree is best done early.

Conclusion

Using these two simple techniques helps both parties enormously. It’s not always necessary and doesn’t need to be an extensive exercise but just enough to ensure a level of understanding on the side of the development, project management and sales team (after all its hard to quote for something you don’t understand).