Sep 12 2011
I asked myself this question straight out of college when I was being plugged into a testing role for my very first project. Fast forward about 7 years later, I still find folks confusing the two. That's why I decided to try separating the two based on what I've been exposed to.
You'll find various job postings, project roles and position titles fluctuating between the two. However, I believe there is a fundamental difference, especially at the level of manual testing. The following comparisons assume a scenario by which a Tester and a Software Quality Assurance Analyst are provided with test cases already designed with test steps developed.
Aug 17 2011
Dear Bob Lambert, my esteemed friend and colleague, I read your article regarding your opinion that rugby is not a good analogy for agile software development. I respectfully disagree. Like you, I’m also a fan and former player. (Go James River Women!!). As a certified Scrum Master, I strongly believe that Agile is a great way to deliver software. In fact, so does Billy Tilson, another CapTech Rugger. Here’s my take on why our favorite sport is a great analogy for Agile:
Agile Software Development
Aug 11 2011
Most project managers have experienced projects with too few resources or a staff with insufficient skillsets. Specifically within the health care industry, the skillsets are in short supply due to the complex nature of health care; the ideal business analyst may be a nurse with an IT background. There is a sundry of knowledge, code sets, processes, jargon, and vendor systems that can differentiate one resource from another. How do you overcome all of that and find the ideal candidate that can hit the ground running? Developing a creative resourcing approach is usually a part of any project manager's role when resources are scarce.
1) Hire resources with a very strong IT background who will build their own knowledge about your environment and health care. Any health care background may be acceptable, even though it isn’t directly within the same area.
Jul 27 2011
Spotlight on M&A Systems and Data Considerations
This blog will focus on the technology component of M&A and secondarily recognize the impact to people and processes that any large change in technology engenders. Technological systems are a critical piece of any business today and are instrumental in supporting large scale growth without proportional expense growth. While a merger creates technological risk, it also provides an opportunity to upgrade systems in a way that seldom can be organically justified. Mergers present a time for courage and clear direction as succumbing to the inherent political battles over system superiority will create decades of extra expense and reduced agility.