The topics covered in this HowTo include:
- What are HowTo’s
- Why HowTo’s @ PPA
- Why We Wrote HowTo Create A Performance Budget
- What Are Non Functional Requirements
- So What Are Performance Budgets
- What Tiers Should Be Considered In Scope When Defining Performance Budgets
- How Does Performance Budgets Align With Non Functional Requirements
- How Important Are Performance Budgets
- Who Should Own, Design and Maintain Performance Budgets
- At What Point In The Development Life Cycle Should Performance Budgets Be Created
- Let’s Create A Performance Budget
- What Outcomes Should You Expect To Achieve With Performance Budgets
- Measuring and Tracking How Teams Are Tracking With Their Performance Budgets
- Caveats And What To Be Careful Of When Designing Performance Budgets
What Are HowTo’s: A HowTo is a document that does precisely what the name suggests i.e. It’s describes “HowTo” achieve a set of outcomes through illustration of all the steps involved. HowTo’s are generally structured and written without too much technical jargon in a straight forward manner without making too many assumptions of the depth of knowledge the reader. HowTo’s are meant to make for easy reading and are logical in the sequence of steps it recommends.
Any background knowledge to assimilate the information provided in the HowTo is generally highlighted at the start of the HowTo. HowTo’s are generally written for the professional who are clear of what they need to accomplish but have little or no knowledge of how to go about achieving those objectives. HowTo’s are meant to be exhaustive in nature and they are definitely not meant to offer the most efficient way of getting the job done. A HowTo should be seen as a kick starter that helps the user get up and running with a given task without having to master all the required fundamentals.
Why HowTo’s @ PPA: HowTo’s have been the mainstay of the Open Source and Free Software movement for decades. One of the reasons why Open Source and Free Software is so widely used today is simply because of the depth of documentation that exists and the maturity of the Open Source ecosystem which has delivered scalable, open and reliable software. HowTo’s like many other building blocks have helped the Open Source and Free Software movement grow immensely while eliminating the need to keep re-inventing the wheel. It’s only natural that we at Practical Performance Analyst adopt the best from the Open Source and Free Software movement. A lot of the work we do at Practical Performance Analyst borrows from the fundamentals of the Open Source movement and HowTo’s are definitely one of them.
As HowTo’s @ PPA grows and matures we will hopefully reduce the reinventing of the wheel which happens so very often at organizations, projects and programs when it comes to the science of building/delivering systems that scale.
Links to Content –
- HowTo Create A Performance Budget – Part I
- HowTo Create A Performance Budget – Part II
- HowTo Create A Performance Budget – Part III
- HowTo Create A Performance Budget – Part IV
- HowTo Create A Performance Budget – Part V
- HowTo Create A Performance Budget – Part VI
- HowTo Create A Performance Budget – Part VII
James White (LinkedIn) – James has over 10 years of experience in developing and maintaining Java Architectures. As part of prior roles James has experience managing both on and off shore teams. He’s also recently been certified as an Accenture Certified Technical Architect. Prior to Accenture, James worked as a senior developer for Delta Dental where he was the primary developer for the company’s most critical application which processed billions of dollars worth of dental claims annually. James has also worked as part of the performance testing team and has experience in developing test scripts for load and stress testing.
Trevor Warren (Linked In) focuses on building innovative solutions that have the potential to impact people’s lives in a positive manner. Trevor is inquisitive by nature, loves asking questions and sometimes does get into trouble for doing so. He’s passionate about certain things in life and building solutions that have the ability to impact people’s lives in a positive manner is one of them. He believes that he can change the world and is doing the little he can to change it in his own little ways. When not hacking, building new products, writing content for Practical Performance Analyst, dreaming up new concepts or building castles in the air, you can catch-him bird spotting (watching planes fly above his house). You can reach trevor at – trevor at practical performance analyst dot com. The views expressed on this web site are his own.