Competencies versus Roles: We’ve seen a positive move toward emphasizing competencies in a team rather than roles or titles. As teams make that change, we see fewer “It’s not my job” excuses and more “How can I help?” conversations. Team members will continue to have core competencies in some areas more than others, but they may not identify as strongly with a particular role. For example, saying, “I am a tester” really means, “I perform mainly testing activities because that is my primary passion and strength. I can provide leadership ...
Methods & Tools â€“ the free e-magazine for software developers, testers and project managers â€“ has just published its Spring 2015 issue that discusses Impact-Driven Scrum, Code Review, #NoEstimates,Self-Selecting Teams, Software Laws, Kanboard and ConQAT.
* Impact-Driven Scrum Delivery
* Code Review: Why It Matters
* #NoEstimates – Alternative to Estimate-Driven Software Development
* Self-Selecting Teams Part 2 – Keeping the Momentum
* Laws for Software Development Teams
* Kanboard – Open Source Kanban Board
* ConQAT â€“ The Continuous Quality Assessment Toolkit
50 pages of software development knowledge that you can freely download from http://www.methodsandtools.com/mt/download.php?spring15
[…] Seilevel Blog – Visit this site for relevant and timely articles on Business Analysis. The authors are business analysts who write about their work and what they’ve learnt on the job. The tips you get from this site are practical and can be applied to your projects. […]
Software architecture and coding are often seen as mutually exclusive disciplines, despite us referring to higher level abstractions when we talk about our software. You’ve probably heard others on your team talking about components, services and layers rather than objects when they’re having discussions. Take a look at the codebase though. Can you clearly see these abstractions or does the code reflect some other structure?
If so, why is there no clear mapping between the architecture and the code? Why do those architecture diagrams that you have on the wall say ...
Here is our monthly selection of knowledge on programming, software testing and project management. This month you will find some interesting information and opinions about software development culture, project estimation, checking the health of your project team, the costs and benefits of unit testing, product backlog management, mobile architecture, test coverage and user experience.
Blog: Culture Change: Reinventing Organizations
Blog: Why you suck at estimating â€“ a lesson in psychology
Blog: Squad Health Check model â€“ visualizing what to improve
Blog: Selective Unit Testing â€“ Costs and Benefits
Article: The Significance of Release Retrospectives
Article: Mobile ...
Having some decade of experience in software development behind me, I had the time to accumulate a lot of mistakes. One of the recurring patterns in these failures was the ambition to solve code issues too quickly. This was especially the case when the problem was related to code that I wrote, which made me feel responsible for the situation. Naturally, I had also often think that my code couldn’t be bad and somebody must have changed it after I deliver it, but this is another story ;O)
When you detect ...
During the search for a better, easier ways to create images to represent software concepts, I’ve come across a few tools that do a good job creating basic, official-looking graphs. Many of these tools offer teaser trials in hopes of inducing you to buy a full featured version. Not so with the open web app […]
QCon London, March 2-6 2015, London, UK
Exclusive 50 pounds Method & Tools discount with promo code â€śsoftdevconf50â€ł
Wearables TechCon, March 9-11 2015, Santa Clara, USA
Use code WEARIT for a $200 conference discount off the 3-day ...
Being a consultant can sometimes be awkward. You get to a client site, and you are expected to work with brand new people who you may have never met. These people do not know your skill-set, theyâ€™ve never seen your work or heard your reasoning, and in some cases they might be wondering why youâ€™ve […]
I recently participated in a Panel Discussion on the state of the Business Analyst Profession held by IIBA of Austin. One of the questions we tackled was the following: “What are the key traits that a Business Analyst must possess?” There are many qualifications and abilities that a good analyst must possess. The ability to […]
I get asked about my favorite tips and tricks for writing stories in an agile backlog.Â One of my tips is to make it EASY for the engineers â€“ give them â€śone stop shoppingâ€ť.Â Engineers arenâ€™t lazy, but they donâ€™t like having to hunt about for the documents and other artifacts they need to be […]
Here is our monthly selection of interesting knowledge material on programming, software testing and project management. This month you will find some interesting information and opinions about software and system modeling, programmer psychology, managing priorities, improving software architecture, technical user stories, free tools for Scrum, coding culture and integrating UX in Agile approaches.
Web site: Fundamental Modeling Concepts The Fundamental Modeling Concepts (FMC) primarily provide a framework for the comprehensive description of software-intensive systems.
Blog: The Ten Commandments of Egoless Programming
Blog: WIP and Priorities: Hw to Get Fast and Focused!
Blog: Sacrificial Architecture
Roses are red Violets are blue Weâ€™re going agile, How about you? Itâ€™s 6 weeks into the year and I know at least a handful of you are working for organizations who set a 2015 initiative to transform IT to agile practices. So howâ€™s it going? Given we are 6 weeks into the year, and […]
I am a firm believer that any situation in life or in business can be traced to an episode of either The Simpsons or Seinfeld. In The Simpsons season 2 episode â€śOh Brother, Where Art Thou,â€ť the patriarch of the Simpson family designs a car, which provides a surprisingly sophisticated look into project team dynamics. […]
The worrying thing about writing tests is that there are numerous accounts of people introducing tests into their development process and.. ending up with even more junk code to support than they had to begin with! Why? I guess, mainly because they lacked the knowledge and understanding needed to write good tests: tests, that is, that will be an asset, not a burden.
Reference: Bad Tests, Good Tests, Tomek Kaczanowski, http://practicalunittesting.com/btgt.php
â€śYou donâ€™t tell the market what you are selling, the market tells you what it will buyâ€ť - I talk to a lot of people about starting businesses and a lot of them still think that a comprehensive business plan that takes months to develop is a key component to starting a business. It turns […]
I’ve been working on a program that has certain been a challenge, both from the subject matter, the extremely short timeframes given (imposed governmental regulations that must be met), to the stakeholders (who have day jobs to perform as well). Everyone is under pressure, which can make for some short fuses as well as poor […]
I was once part of a teamÂ atÂ a consumer-facing technology company, who described themselves as incredibly fast-paced, operating within a rapidly changingÂ environment. This team was smaller (4 developers in a 10-person business unit), so I expected the ability to get things done quickly to be one of our strengths. Upon joining, I was surprised to hear […]
â€śReductionism: The theory that every complex phenomenon â€¦ can be explained by analyzing the simplest, most basic physical mechanisms that are in operation during the phenomenon.â€ť Think about any software product that you have ever used. For the most part, you care about the whole of the product, which is the collective effort of all […]
SPTechCon, February 8-11 2015, Austin, USA
Use code SHAREPOINT for a $200 conference discount off the 3 and 4-day pass
NorDevCon, February 27 2015, Norwich, UK
Early birds tickets until February 13.
QCon London, March 2-6 2015, London, ...