Documentation and Developer Onboarding
Organizations that build and support software have many unique challenges. They also have quite a few common challenges. One of those is how to help new technical team members come up to speed on the technical environment, coding standards, naming conventions, code base, build and deploy tooling, version control standards and conventions, and so forth. Not long ago, someone posted a question on Tw
The Impact Your Teaming Strategy Has on Velocity
Teams in Agile are a very specific construct. Teams are made up of six to eight people…sometimes a person or two more, sometimes a person or two less…but the idea is that everyone should be able to talk to everyone else and pay attention to what each other are doing. They should be able to work together. They should be able to collaborate with each other. They should know each other. Teams should
User Stories Don't Work for our Team
Here’s one I hear all too often (paraphrased): “Our team doesn’t support customer-facing application software. We support a set of internally-consumed APIs for our SOA environment. Therefore, we can’t use User Stories. The User Story is one way of describing a piece of work to be done. The canonical form “As a something I want something so that something” is only an example to help people get star
How developer maturity affects building teams.
A conversation with SVP, Senior Consultant Marty Bradley about how developer maturity plays a role in forming software development teams. Hey Marty, so what’s the difference between a programmer, developer, engineer or consultant? To me the biggest distinction is that developers don’t do things more than once. For example, one of the first things we try to get a team to do is move towards at least
12 Key Knowledge Areas for Agile
I think this is going to be my last 12 point list for the week. It’s not like I’m out of time or anything… the snow melted a little yesterday… but we are still pretty much iced in. We are going to brave heading out to the grocery store this afternoon and maybe have lunch out again. Past that, we are all hunkered down hoping that the sun comes out and warms us up a bit. After this one, I’ve got one
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
What I Learned Co-Training a CSM Class
Should We Have a WIP Limit For Organizational Change?
A Day Without a ScrumMaster
Agile Budgeting: How to Calculate For Agile Teams
Agile 101 - Presented at the PM Symposium
Sprint Planning Meeting: A Simple Cheat Sheet
Getting Testing Involved
Why Estimate?
Why Organizations Should Have a Product Owner Team
12 Assumptions Agile is Making About Your Company
12 Keys to Success with Agile
LeadingAgile: How to Own a Really Big Complex Product #agile2010
Okay... Just What are we Transforming?
Leading Agile: Scaling Agile Past the Team - Agile Dev Practices Edition
Leading Agile: The Gist of My Agile Dev Practices Talk