Abstract: Extreme Programming (XP) is a lightweight software development methodology. It attracts attention of many software development teams and its popularity is growing very fast. A part of success comes from interesting composition of programming practices included into XP. But what particularly appeals to programmers and makes XP especially interesting to them is resignation of inspection meetings, thick documentation etc. Many people do not understand XP and they find XP a good excuse for not using approved programming practices. Thus, a maturity model for XP is needed that would indicate the risk associated with a project and in some cases made it clear that a project is not following neither CMMISM nor XP practices. In the paper we propose a simple 4-level maturity model for XP.