looneypuffpmp.blogspot.com
The Corner Cube PM: June 2011
http://looneypuffpmp.blogspot.com/2011_06_01_archive.html
The Corner Cube PM. Smile, take a deep breath, and go at it again! Friday, June 24, 2011. When was the last time you say “thank you” to your team members? Did you remember the most recent occurrence where you acknowledge a team member’s effort? Did you acknowledge the effort personally or publicly? 8211; Do not delay in showing the appreciation; make it as immediate as possible. 8211; Mention the exact behaviour that is notable for the recognition. In rewarding, it is also good to remember the team groun...
looneypuffpmp.blogspot.com
The Corner Cube PM: Getting to Know the Stakeholders
http://looneypuffpmp.blogspot.com/2011/07/getting-to-know-stakeholders.html
The Corner Cube PM. Smile, take a deep breath, and go at it again! Monday, July 25, 2011. Getting to Know the Stakeholders. There are many reasons why you should Identify Stakeholder. Early in the project life cycle. Most important reason is that, your stakeholders can influence the direction of the project. Based on the information that they share with you or the things that they say to other people, your project is impacted by them. Alice in customer support team. How do they respond to questions?
codeforlife.org
Code for Life: February 2011
http://www.codeforlife.org/2011_02_01_archive.html
Personal and professional points of view. Monday, 28 February 2011. What's Wrong With The Way We Write Software? Lately, I've realized that when discussing "what's wrong with the way we write software? That I've been starting out on the wrong foot. The clue is in the question: there's not really that much wrong with the way we write. It's all to do with the way we design. If you're not typing, you're not developing. So why do we still talk about "writing" software? Some good ideas here). Time at the ...
codeforlife.org
Code for Life: May 2012
http://www.codeforlife.org/2012_05_01_archive.html
Personal and professional points of view. Tuesday, 1 May 2012. How Bad Code Commit Habits Hide Problems. I was initially inspired to write a few words on these matter by this post. And Ive been reminded to finish it by the new tester on my team, Sona, whos come from a class IV medical devices background, where their auditor insisted. That every single commit was linked to a defect or change request ID. Links to this post. Subscribe to: Posts (Atom). View my complete profile. Agile in a Flash. Link: How W...
codeforlife.org
Code for Life: Anti-Pattern #3: Cheat To Win
http://www.codeforlife.org/2012/07/anti-pattern-3-cheat-to-win.html
Personal and professional points of view. Saturday, 14 July 2012. Anti-Pattern #3: Cheat To Win. If ever there was a phrase that I've heard in project management that made me immediately worry, it was "Cheat To Win". You maybe need some more context to understand, and perhaps some alternative phrasings that may ring a bell. Try "Quick and Dirty" or perhaps even "Low Hanging Fruit". Ringing any bells? Good No, that's bad! Who (or what) are we cheating? What is it we're trying to win? Leaking information (...
codeforlife.org
Code for Life: Anti-Pattern #4: Give Work To The Lowest Bidder
http://www.codeforlife.org/2012/07/anti-pattern-4-give-work-to-lowest.html
Personal and professional points of view. Wednesday, 25 July 2012. Anti-Pattern #4: Give Work To The Lowest Bidder. To start with, it's worth me being specific about the type of work and the type of bid I'm talking about: it's for agreed scope and quality software work, but not fixed price. With a contractor, or even an internal division, team, or individual. So you all know how this works already! I'm rather tired of people in the same company talking about negotiating with each other when we're on the ...
codeforlife.org
Code for Life: May 2013
http://www.codeforlife.org/2013_05_01_archive.html
Personal and professional points of view. Thursday, 30 May 2013. My First Marathon: From Fantasy, Through Reality, To Missing The Target, But Still Being Proud. Tens of thousands of people do London year after year, with preparation ranging from excellent through to bugger all. How hard can it be right? Very, very hard as it turns out. After this mammoth run, the taper began, and everything started to slot into place. I was starting to find my target 8 minute mile pace easier to lock down (although I...
codeforlife.org
Code for Life: Software Project Management Anti-Patterns
http://www.codeforlife.org/2012/06/software-project-management-anti.html
Personal and professional points of view. Thursday, 7 June 2012. Software Project Management Anti-Patterns. Anti patterns are often a great way to sum up the thinking behind a set of patterns by stating a small, highly exemplifying set that sums up exactly what we shouldn't do. In some cases, they are the best or only way, because the patterns we want to communicate aren't quite so easy to elucidate, are too many, or too varied. In no particular order:. All projects equally late. View my complete profile.
codeforlife.org
Code for Life: October 2012
http://www.codeforlife.org/2012_10_01_archive.html
Personal and professional points of view. Wednesday, 10 October 2012. Anti-Pattern #5: Always Finish The Job. But things arent quite so simple in our professional lives: things change, and things can change pretty damn fast. Links to this post. Subscribe to: Posts (Atom). I am Iain Charlton, a family man from Farmoor, who is also engineering manager of Oxehealth. And a board member of the Biomedical Engineering Association. View my complete profile. Engineering in Medicine and Health. Agile in a Flash.
codeforlife.org
Code for Life: April 2011
http://www.codeforlife.org/2011_04_01_archive.html
Personal and professional points of view. Thursday, 7 April 2011. Usability Design of a Micro System Clock. I just bought my wife a lovely Birthday present: a DVD micro system (Philips DCD 377) to replace her very tired CD micro system in our bedroom. There was one thing on the old system that I was confident the new one could easily match: and LCD display with a clock on it. How wrong was I. And just how is it possible to get the design of a clock so wrong? Two big problems with the design here:. And a ...
