I was involved in the Beta testing of Daylite Touch for the iPad and was invited to write a case study describing how my business benefits from using Daylite and Daylite Touch for iPad. Here’s the published case study.
Archive for the ‘gtd’ category
My Daylite Touch for iPad case study
December 16th, 2010Awesome tools for rapid UX prototypes – Letting you focus on the solution!
June 18th, 2009Comic Life is great for creating story flows in a rough and ready way, with a little style.
Balsamiq is an excellent tool for rapidly creating purposefully low-fi wireframe mockups
Napkee enables you to import Balsamiq mockups and turn them into HTML prototypes! Lovely!
Axure is excellent for rapidly creating interactive prototypes.
Liferay Portal is a pretty awesome portlet container that, with a bit of UX (HTML, CSS and JSP) hacking, enables you to rapidly produce fully functional portals. It comes with a vast array of portlets out of the box, saving you a whole load of time.
JQueryUI is a lovely toolkit for quickly developing interactive prototypes. I’m not completely convinced by it as a production tool (heavy JS? but i could be wrong), but excellent for prototyping
Summary of my adoption of GTD
March 9th, 2009http://web.me.com/andygoundry/OmniFocus_Review/
It’s only a draft, but it’s a start. More to follow…
Omnifocus – getting more beautiful by the day
December 2nd, 2008I have many notes on my use of OmniFocus on mac and iPhone to GTD but none quite ready to post. But, if you your’re not Getting Things Done or are on a mac and are not using OmniFocus, perhaps you should! It’s lovely!
Dave Thomas: Security as a measure of effectiveness
October 26th, 2008I really like this approach – Assess the state of security within a development team and project as an indication of how well a project is going and how effective processes are working out.
It’s another one of those many obvious tests that we all do, but at times i’ve certainly found myself accepting insecurity within a project team as one of those things because the team are new to the pressures or software projects are always uncertain and as such stressful. With a little consideration, it’s clearly more useful to use perceptions of insecurity as more direct indications that change is required.
What might we be looking for? A few possible ideas:
- How secure are the developers about the quality and stability of their code?
- How secure are the developers about rolling code to the various hosting platforms?
- How secure are team members about their relationship with others on the team?
- How secure is the project manager about hitting the deadline?
- How secure is the account manager about conversations with the client?
- How secure are senior management about project and team performance?
The overall intention of improving security is to make everyone feel relaxed. Software development is meant to be fun after all!
Source: Agile Toolkit Podcast ‘No fluff just stuff 2006 tour’
