I had a little free time over lunch so I browsed on over to to the latest CIO articles quickly and came across a series of three that I quite enjoyed: "Three Keys to Getting Your Projects Under Control"
Part 1 (Plug Leaks)
Part 2 (Have an Idea)
Part 3 (Go Granular)
The series attracted my attentions as I recently attended the BCS miniSPA event which is a summary of the 6 most highly voted sessions from the real SPA event held in March earlier this year.
At the miniSPA, I attended Marina Haase's workshop on Best Practices for Finding your way into new Projects - quickly....
Other than the ?obviously huge? amount of good ideas that attendees put forward during the individual brainstorming slot, Marina also introduced us, during the group work, to Analogy/Metaphorical Brainstorming techniques which I had heard about and practiced a little privately on some problems, but never in a group. The effects were pretty amazing and I definitely recommend you find out more about the technique and try it!
Edward De Bono also promotes using analogies for creative thinking in his books on Lateral Thinking and The 6 Thinking Hats. Although he advocates random selection techniques for the selection of the scenario that needs to pull/generate ideas.
Showing posts with label recommendation. Show all posts
Showing posts with label recommendation. Show all posts
Wednesday 30 July 2008
Wednesday 23 July 2008
Scaling Software Agility by Dean Leffingwell
Dean is the former founder and CEO of Requisite Inc, responsible for the Requirements Gathering and Analysis Tool: Requisite Pro. It seems like his vast experience from startup to merging with IBM has touched on a number of key software development issues and he is now consulting very successfully and writing good books!
I picked up Scaling Software Agility at a book store/stall at SPA 2008 as it seemed to have a couple of new things to say, or at least say them in new ways - and I was very pleased with my choice!
I believe there is something for everyone in this book - wether you are new to agile or an experienced practitioner. The book touches on a number of topics and leads you from brief "beginner" chapters through to more interesting ones that are very relevant in today's software development arena - the scaling of agility.
Things that stand out in my memory of this book are the application of valuable software quality and management metrics, and the many strategies that Dean suggests can be used to counter the arguments typical organisational "police" will use to counter the attempt to "go [more] agile" and potentially inadvertently lead to "acceptable failure" or worse, "death march".
Usually corporations do not react to the infiltration of agile practices as they are kept within [small] team perimeters, thereby "flying under the radar". If you have a requirement to scale agile, then by definition you clearly have more people and teams that you are concerned about. There is more visibility and attention from the people who might strategically oppose the changes they do not understand, and/or department(s) or programme(s) it is being attempted in - key strategic people that you never previously even knew existed, nor what their concerns were, are now watching your every move.
http://www.amazon.co.uk:
http://www.amazon.com:
Reason 2: Part 2 follows with more depth about the 7 Agile Practices that work: Agile Component Team, Agile Planning and Tracking, Iterations, Small Frequent Releases, Agile Testing, Continuous Integration, Retrospectives.
Reason 3: The 7 practices Leffingwell recommends for Scaling Agile:
- "Intentional Architecture": Approaches on how to tackle large software systems with Agile Architecture
- "Scalable Lean Requirements": Three simple topics that avoid analysis-paralysis failure mode: vision, roadmap and just-in-time (JIT) elaboration
- "Systems of Systems and the Agile Release Train": how to plan, and deliver, complex software components with interdependencies
- "Managing Highly Distributed Development": It is very difficult, and is a problem all successful software programmes face. Sooner or later the team is too big to fit in 1 room, on 1 floor, of 1 building, of 1 city, of 1 country. Inevitably practices have to be developed that can assist software that is developed by many different people, in different locations
- "Impact on Customers and Operations": How marketing, or product owners, or programme owners, will be convinced that Agile is a good thing for them
- "Changing the Organisation": How to address the arguments and fallacies that the corporate immune system is going to throw around as things become more agile
- "Measuring Business Performance": Real, usable, useful management metrics that can be used to control and manage large scale [agile] software development efforts
Thankyou for reading my recommendations!
I picked up Scaling Software Agility at a book store/stall at SPA 2008 as it seemed to have a couple of new things to say, or at least say them in new ways - and I was very pleased with my choice!
I believe there is something for everyone in this book - wether you are new to agile or an experienced practitioner. The book touches on a number of topics and leads you from brief "beginner" chapters through to more interesting ones that are very relevant in today's software development arena - the scaling of agility.
Things that stand out in my memory of this book are the application of valuable software quality and management metrics, and the many strategies that Dean suggests can be used to counter the arguments typical organisational "police" will use to counter the attempt to "go [more] agile" and potentially inadvertently lead to "acceptable failure" or worse, "death march".
Usually corporations do not react to the infiltration of agile practices as they are kept within [small] team perimeters, thereby "flying under the radar". If you have a requirement to scale agile, then by definition you clearly have more people and teams that you are concerned about. There is more visibility and attention from the people who might strategically oppose the changes they do not understand, and/or department(s) or programme(s) it is being attempted in - key strategic people that you never previously even knew existed, nor what their concerns were, are now watching your every move.
http://www.amazon.co.uk:
http://www.amazon.com:
Why I recommend Scaling Software Agility:
Reason 1: Part 1 covers the essentials of Agile, Waterfall, XP, RUP, Scrum, Lean Software, DSDM, FDD in 85 pages!Reason 2: Part 2 follows with more depth about the 7 Agile Practices that work: Agile Component Team, Agile Planning and Tracking, Iterations, Small Frequent Releases, Agile Testing, Continuous Integration, Retrospectives.
Reason 3: The 7 practices Leffingwell recommends for Scaling Agile:
- "Intentional Architecture": Approaches on how to tackle large software systems with Agile Architecture
- "Scalable Lean Requirements": Three simple topics that avoid analysis-paralysis failure mode: vision, roadmap and just-in-time (JIT) elaboration
- "Systems of Systems and the Agile Release Train": how to plan, and deliver, complex software components with interdependencies
- "Managing Highly Distributed Development": It is very difficult, and is a problem all successful software programmes face. Sooner or later the team is too big to fit in 1 room, on 1 floor, of 1 building, of 1 city, of 1 country. Inevitably practices have to be developed that can assist software that is developed by many different people, in different locations
- "Impact on Customers and Operations": How marketing, or product owners, or programme owners, will be convinced that Agile is a good thing for them
- "Changing the Organisation": How to address the arguments and fallacies that the corporate immune system is going to throw around as things become more agile
- "Measuring Business Performance": Real, usable, useful management metrics that can be used to control and manage large scale [agile] software development efforts
Thankyou for reading my recommendations!
Building Scalability and Achieving Performance
This is a short and very useful read on scaling architectures - InfoQ got 3 key architects with backgrounds in Twitter, eBay and Betfair to share their experiences, some approaches they take, and some tool recommendations. Practical advice! Building Scalability and Achieving Performance.
Friday 18 July 2008
Ethical Office Politics
I have been meaning to read this article for about a month now, and finally got the time this morning! Adrian, the author of the article, covers quite a few topics throughout the piece and I found it an insightful and well thought out argument.
Ethical Office Politics
I think he does a good job of most of the issues I have studied, heard about, thought about and/or experienced.
Ethical Office Politics
I think he does a good job of most of the issues I have studied, heard about, thought about and/or experienced.
Monday 23 June 2008
What does it really take to secure a chip-n-pin debit card?
I've just had my second chip-n-pin debit card blacklisted within a year due to failed overseas fraudulent cash withdrawal attempts!
The fraudsters are stealing enough of my highly secure chip details, plus identifying my darn PIN when I enter it (VERY) carefully. Luckily for me, I have not changed many of the places that I normally use chip-n-pin in the past year so I have to only stop using it at 2 large trusted and very popular retailers, 1 local convenience retailer, and 2 places where I occassionally get food.
My instinct at the moment is that the theft is occurring inside 1 of the 3 retailers. Lovely stuff!
It occurs to me that the only thing left to do, is not to use chip-n-pin anywhere but at a highly secure ATM, and the cashier inside a bank, on a floor or two above ground!!
But what I don't fully understand is that it seems the thieves are happy to walk away with just 1 entry per location per day/week/month, thereby leaving the bank investigators no pattern that they can use to crack these networks. And these networks must be very well connected with some tiny electronic goodies, some fairly secure channels of communicating with each other in some non-pattern-recognisable manner, and some even more intricate chip programming and card producing facilities. There must surely be some way of looking at enough of the data the banks hold on these things and discovering some patterns - humans are just not capable of not having patterns!
Anyway, whatever the banks are doing so far is working - they apparently rejected these 2 withdrawal attempts due to the fact that they were not consistent with my usage pattern.
Hmmm ... "pattern" has now come up 4 times in this entry. Perhaps the recommendation for chip-n-pin users is actually: create a distinct very small pattern of usage - I do not believe at this time that the law will stop the thiefs, and it is only a matter of time before they're generating all the valid numbers and PINs they can dream of (maybe they already are...then I can actually use mine again!!??!?).
Grrrr!
The fraudsters are stealing enough of my highly secure chip details, plus identifying my darn PIN when I enter it (VERY) carefully. Luckily for me, I have not changed many of the places that I normally use chip-n-pin in the past year so I have to only stop using it at 2 large trusted and very popular retailers, 1 local convenience retailer, and 2 places where I occassionally get food.
My instinct at the moment is that the theft is occurring inside 1 of the 3 retailers. Lovely stuff!
It occurs to me that the only thing left to do, is not to use chip-n-pin anywhere but at a highly secure ATM, and the cashier inside a bank, on a floor or two above ground!!
But what I don't fully understand is that it seems the thieves are happy to walk away with just 1 entry per location per day/week/month, thereby leaving the bank investigators no pattern that they can use to crack these networks. And these networks must be very well connected with some tiny electronic goodies, some fairly secure channels of communicating with each other in some non-pattern-recognisable manner, and some even more intricate chip programming and card producing facilities. There must surely be some way of looking at enough of the data the banks hold on these things and discovering some patterns - humans are just not capable of not having patterns!
Anyway, whatever the banks are doing so far is working - they apparently rejected these 2 withdrawal attempts due to the fact that they were not consistent with my usage pattern.
Hmmm ... "pattern" has now come up 4 times in this entry. Perhaps the recommendation for chip-n-pin users is actually: create a distinct very small pattern of usage - I do not believe at this time that the law will stop the thiefs, and it is only a matter of time before they're generating all the valid numbers and PINs they can dream of (maybe they already are...then I can actually use mine again!!??!?).
Grrrr!
Tuesday 10 June 2008
Mastering The Art of War
I have just finished a rather quick and easy to read book about some of the subtleties of life, people, strategy, change and organisation. A good start to a blog to changes and challenges and embracing all of life!
Mastering The Art of War touts itself (or its authors - Liu Ji and Zhuge Liang, or its translator Thomas Cleary does) as exploring some of the wisdoms of two books of ancient Chinese origin: Sun Tzu's The Art of War (a book about strategy) and I Ching - (the Book of Changes containing 360 insights to help people deal with change - 1 for each day of the lunar year). I have not read either yet, but now am more than ever looking forward to the time and place!
One of the extracts from Mastering the Art of War I keep thinking about (especially in terms of "things no one taught me at school!")
1. Question them concerning right and wrong, to observe their ideas
2. Exhaust all their arguments, to see how they change
3. Consult with them about strategy, to see how perceptive they are
4. Announce that there is trouble, to see how brave they are
5. Get them drunk, to observe their nature
6. Present them with the prospect of gain, to see how modest they are
7. Give them a task to do within a specified time, to see how trustworthy they are"
Reason 2: It has been 2 weeks since I finished it, and I am still thinking back to some of the wisdom from some of the pages, hence I am "forced" to blog about this book now (when I really don't have time!)
Reason 3: There are many pearls and interesting historical stories of China's history and ancient ways of life - such as the one I extracted above.
This one seems to be the most popular amazon.co.uk seller for I Ching (ranked 28632 today) . According to Mastering The Art of War, the I Ching is not supposed to be used for divination purposes at all - a rule that was once strictly adhered to in ancient times when it was decreed forbidden to do so!
Mastering The Art of War touts itself (or its authors - Liu Ji and Zhuge Liang, or its translator Thomas Cleary does) as exploring some of the wisdoms of two books of ancient Chinese origin: Sun Tzu's The Art of War (a book about strategy) and I Ching - (the Book of Changes containing 360 insights to help people deal with change - 1 for each day of the lunar year). I have not read either yet, but now am more than ever looking forward to the time and place!
One of the extracts from Mastering the Art of War I keep thinking about (especially in terms of "things no one taught me at school!")
 |
| Mastering The Art Of War Is Full Of Personal Wisdom Anecdotes |
"Hard though it may be to know people, there are ways:
1. Question them concerning right and wrong, to observe their ideas
2. Exhaust all their arguments, to see how they change
3. Consult with them about strategy, to see how perceptive they are
4. Announce that there is trouble, to see how brave they are
5. Get them drunk, to observe their nature
6. Present them with the prospect of gain, to see how modest they are
7. Give them a task to do within a specified time, to see how trustworthy they are"
Why I recommend Mastering The Art of War:
Reason 1: It is really short, condensed, well written and edited, and reads very quicklyReason 2: It has been 2 weeks since I finished it, and I am still thinking back to some of the wisdom from some of the pages, hence I am "forced" to blog about this book now (when I really don't have time!)
Reason 3: There are many pearls and interesting historical stories of China's history and ancient ways of life - such as the one I extracted above.
This one seems to be the most popular amazon.co.uk seller for I Ching (ranked 28632 today) . According to Mastering The Art of War, the I Ching is not supposed to be used for divination purposes at all - a rule that was once strictly adhered to in ancient times when it was decreed forbidden to do so!
These 2 are also highly recommended on the respective .co.uk and .com Amazon sites! But there are many options clearly in this space so pick one that makes best sense to you!
Thankyou for reading!
Tuesday 13 May 2008
Lean Software Development
I've been working in "officially" agile environments now since 2000, mainly influenced by Scrum and some eXtreme Programming. A while ago a I did a course on Lean Management amongst other topics and was struck by how some similar concepts (just in time, prioritised work queue, continuous reduction of waste, skilling people, empowering people) seem to be in agile.
The chance to get into my copy of Lean Software Development by Mary and Tom Poppendieck finally came along a few weeks ago after seeing it being referred to in high regard on the web and liking the essays I found on their web site: The Poppendiecks. Basically - "WOW"! This is just really really good stuff. For me it is the kind of jump (up or forward I am not sure) that Scrum makes from Agile fundamentals to real world tools that are completely understandable and easy to try.
The great thing is that they concentrate on fundamentals and then supply thinking tools to help you apply them in your context - ie, they KNOW the lesson that Best Practices are awful as it is the fundamental that must be understood and copied from one context to another to be successfully applied in the new context. Too many Best Practices have resulted in failure and too much waste for my liking!
They touch on some fundamental concepts that are important in modern software development:
- waste
- learning
- last responsible moment
- fast turnaround
- team empowerment
- perceptual and conceived integrity
- holistic view
Reason 2: Collaboration is better - cross disciplinary people working together are more efficient AND enjoy their work more AND result in a better product AND it is cheaper AND AND AND!
Reason 3: Specific facts, graphs and examples that you can refer to when justifying reasons why you would want to try something different in your own environment, all with a firm basis in Lean Management Theory and which has been studied, well understood, and implemented by some very successful organisations ranging from Toyota to 3M for between 60 and 100 years!!
Thankyou for supporting!
The chance to get into my copy of Lean Software Development by Mary and Tom Poppendieck finally came along a few weeks ago after seeing it being referred to in high regard on the web and liking the essays I found on their web site: The Poppendiecks. Basically - "WOW"! This is just really really good stuff. For me it is the kind of jump (up or forward I am not sure) that Scrum makes from Agile fundamentals to real world tools that are completely understandable and easy to try.
The great thing is that they concentrate on fundamentals and then supply thinking tools to help you apply them in your context - ie, they KNOW the lesson that Best Practices are awful as it is the fundamental that must be understood and copied from one context to another to be successfully applied in the new context. Too many Best Practices have resulted in failure and too much waste for my liking!
They touch on some fundamental concepts that are important in modern software development:
- waste
- learning
- last responsible moment
- fast turnaround
- team empowerment
- perceptual and conceived integrity
- holistic view
Why I recommend Lean Software Development:
Reason 1: Identify the value chain from point of need to point of delivery - it is strongly argued by some that anything but coding for that need fulfilment is just a waste of time. IE - as per Agile - lighter weight documentation, lighter weight project management, focus on delivering real value to the client!Reason 2: Collaboration is better - cross disciplinary people working together are more efficient AND enjoy their work more AND result in a better product AND it is cheaper AND AND AND!
Reason 3: Specific facts, graphs and examples that you can refer to when justifying reasons why you would want to try something different in your own environment, all with a firm basis in Lean Management Theory and which has been studied, well understood, and implemented by some very successful organisations ranging from Toyota to 3M for between 60 and 100 years!!
Thankyou for supporting!
Monday 12 May 2008
7 Things CIOs Should Know About Agile Development
I've been reading CIO articles for a number of years now - it is one of the sources that I find does a lot of integration for me between the domains of business, software development and IT system management - ie technology for business.
7 Things CIOs Should Know About Agile Development is an example of this integration. Often I find myself a little too focussed on my local project's agile process, and not neccessarily on what the "business drivers" are really after, or the Agile messages that might sell them on Agile more effectively. This is a little gentle reminder.
BTW, the shortcut to follow to get a glimpse of this site's value (IMHO): CIO's 50 Most Popular Articles. On this page articles that will definitely entice me back later:
- "You Used Perl/Python/Ruby/PHP to Write WHAT?!" (4 articles for the 4 languages)
- "Windows vs Linux vs OS X"
- "How to Get Real About Strategic Planning"
Thankyou for supporting!
7 Things CIOs Should Know About Agile Development is an example of this integration. Often I find myself a little too focussed on my local project's agile process, and not neccessarily on what the "business drivers" are really after, or the Agile messages that might sell them on Agile more effectively. This is a little gentle reminder.
BTW, the shortcut to follow to get a glimpse of this site's value (IMHO): CIO's 50 Most Popular Articles. On this page articles that will definitely entice me back later:
- "You Used Perl/Python/Ruby/PHP to Write WHAT?!" (4 articles for the 4 languages)
- "Windows vs Linux vs OS X"
- "How to Get Real About Strategic Planning"
Thankyou for supporting!
Wednesday 7 May 2008
Scot's Newsletter Best Firewall Recommendation Made!
After 1.5 years (!!), Scot's Newsletter has reached a conclusion on the Best [Personal] Firewall Software ... (drum roll) ... (more drum roll) ... Online Armor! Read all about it in detail at Scot's Newsletter!
This blog entry by Scot makes for very interesting reading, not just from an interested-in-firewall-software point of view, but also I believe there are some other big concepts clearly "in play":
- the power of online marketing,
- the power of a respected industry leader,
- the influence a key client has over a product's development,
- the ability and agility with which the 2 final contenders were responding to user requests
- and in the future we'll have to see what happens to both companies!
For now, I am still on the previous version of Comodo as I really have not had the time or requirement to migrate, upgrade or change anything else on my home system.
This blog entry by Scot makes for very interesting reading, not just from an interested-in-firewall-software point of view, but also I believe there are some other big concepts clearly "in play":
- the power of online marketing,
- the power of a respected industry leader,
- the influence a key client has over a product's development,
- the ability and agility with which the 2 final contenders were responding to user requests
- and in the future we'll have to see what happens to both companies!
For now, I am still on the previous version of Comodo as I really have not had the time or requirement to migrate, upgrade or change anything else on my home system.
Tuesday 15 April 2008
Six Thinking Hats by Edward De Bono
One of my most influential recent reads: Six Thinking Hats by Edward De Bono. His books have been recommended to me by various people since I was back in first year university. Writing this blog entry has also inspired me to check for his web site and find the Edward De Bono Portal which makes it easy to access other online resources related to him/his thinking creations.
I read Six Thinking Hats directly after reading Lateral Thinking. Both are really excellent reads, but I discovered that I knew quite a bit about lateral thinking already having been exposed to that mode of thought through many people I know socially and have worked with over the years, in some respects it is a natural way for me to approach problems already. Whilst I highly recommend Six Thinking Hats, it contains many references to a number of thinking concerns, thus I believe you need to read at least one of his others, of which I believe none are better choice than Lateral Thinking.
Why I recommend Six Thinking Hats:
Reason 1: Increase in productivity, both my own, and during team based activities such as meetings or workshops.
Reason 2: I, and many software industry people I have met, pretty much rely on a single very useful and relevant style of creating solutions for problems - namely extreme pragmatism. This works well, but is very limited for a future vision, and business people (aka clients) generally are more interested in the future and the environment created for their people.
Reason 3: Increased knowledge of how I think and how others think is invaluable as we are all knowledge workers - aka thinkers.
amazon.co.uk
amazon.com
I read Six Thinking Hats directly after reading Lateral Thinking. Both are really excellent reads, but I discovered that I knew quite a bit about lateral thinking already having been exposed to that mode of thought through many people I know socially and have worked with over the years, in some respects it is a natural way for me to approach problems already. Whilst I highly recommend Six Thinking Hats, it contains many references to a number of thinking concerns, thus I believe you need to read at least one of his others, of which I believe none are better choice than Lateral Thinking.
amazon.co.uk
amazon.com
Why I recommend Six Thinking Hats:
Reason 1: Increase in productivity, both my own, and during team based activities such as meetings or workshops.
Reason 2: I, and many software industry people I have met, pretty much rely on a single very useful and relevant style of creating solutions for problems - namely extreme pragmatism. This works well, but is very limited for a future vision, and business people (aka clients) generally are more interested in the future and the environment created for their people.
Reason 3: Increased knowledge of how I think and how others think is invaluable as we are all knowledge workers - aka thinkers.
Wednesday 20 February 2008
Organizational Patterns of Agile Software Development by James O. Coplien and Neil B. Harrison
Covering a very wide spectrum of software team related issues from distributed remote team participation to architecture, to project control and team building.
This great book is highly relevant and useful in my team lead and architect roles yesterday, today, and I am 100% sure tomorrow also!
James Coplien is quite an interesting guy. I've read a bunch of his essays in the past which have been quite enlightening. You can find them on "Cope's" web site.
Reason 2: In my studies of Organisation Behaviour, Industrial Psychology, Business Management and Human Resource Management, there were a number of consistent themes that were delved into deeply in this book, which has a great deal of real world emphasis and quick illumination, whereas the theory texts are more verbose and not as readily applied.
Reason 3: It is also consistent with my past experiences of organisation behaviours that were dysfunctional as well as those cases where organisations were extremely functional.
Reason 4: Like the Gang of Four's Design Patterns, this book now somehow "lives" in the back of my mind (knowledge was deeply absorbed and incorporated into my thinking without conscious study) so that when I encounter situations I can either more clearly identify what's going wrong, and what possible patterns could be applied, in which possible sequences, in order to address the problem(s), or simply refer to this reference book and delve deeper into the issues and solutions effectively and efficiently.
Reason 5: People I have already referred it to have come back to me and been as astonished by it.
Thankyou for supporting!
This great book is highly relevant and useful in my team lead and architect roles yesterday, today, and I am 100% sure tomorrow also!
James Coplien is quite an interesting guy. I've read a bunch of his essays in the past which have been quite enlightening. You can find them on "Cope's" web site.
Why I recommend Organizational Patterns of Agile Software Development:
Reason 1: It is based on a great deal of research which looks to be scientifically thought out, hypotheses were created, samples statistically selected and information collected and then analysed carefully. So its fairly safe to refer to it and the cases/patterns mentioned that worked or failed.Reason 2: In my studies of Organisation Behaviour, Industrial Psychology, Business Management and Human Resource Management, there were a number of consistent themes that were delved into deeply in this book, which has a great deal of real world emphasis and quick illumination, whereas the theory texts are more verbose and not as readily applied.
Reason 3: It is also consistent with my past experiences of organisation behaviours that were dysfunctional as well as those cases where organisations were extremely functional.
Reason 4: Like the Gang of Four's Design Patterns, this book now somehow "lives" in the back of my mind (knowledge was deeply absorbed and incorporated into my thinking without conscious study) so that when I encounter situations I can either more clearly identify what's going wrong, and what possible patterns could be applied, in which possible sequences, in order to address the problem(s), or simply refer to this reference book and delve deeper into the issues and solutions effectively and efficiently.
Reason 5: People I have already referred it to have come back to me and been as astonished by it.
Thankyou for supporting!
Tuesday 19 February 2008
Agile Project Management - a place to start
Over the past 2 years whenever anyone has asked me "What is Agile Project Management"? or "What is Scrum?" I have been pointing them at Ken Schwaber's talk at Google. Don't get me wrong I am not trying to get into a debate about Scrum, nor about Ken Schwaber, nor even about my Scrum Master Certification.
I do however like this Scrum video as it is a clear and concise summary related (closely) to Agile Project Management that can be absorbed within an hour of time.
Thankyou for supporting!
I do however like this Scrum video as it is a clear and concise summary related (closely) to Agile Project Management that can be absorbed within an hour of time.
Thankyou for supporting!
Scot's Newsletter nearing decision about Personal Firewall Solution!
I have been following Scot's Newsletter for a couple of years now and have especially been following his reviews of personal firewall solutions. I like his reviews because he tests the products from a usability perspective as well as actual firewall security. At the moment the 2 leading providers are pushing Release Candidates faster than he can make a decision because they keep making changes that he has suggested or complained about! (competition is a great thing!)
His 2 leaders at the moment are: Online Armor Personal Firewall and Comodo Personal Firewall. They are both free for personal home use and as a current happy Comodo Firewall user I am watching to see if I should jump ship again. His previous recommendation was Jetico which I also liked.
The latest independent firewall leak test results are really enlightening. Make sure you are safe!
His 2 leaders at the moment are: Online Armor Personal Firewall and Comodo Personal Firewall. They are both free for personal home use and as a current happy Comodo Firewall user I am watching to see if I should jump ship again. His previous recommendation was Jetico which I also liked.
The latest independent firewall leak test results are really enlightening. Make sure you are safe!
Subscribe to:
Posts (Atom)
