Category Archives: Agile

The Shock Therapy according to Scott Downey

The SHOCK THERAPY RECIPE

In order to cut standard Team Discovery or Novice Leadership bootstrapping times by 50% or more, the following steps were used at MySpace when orienting the teams into a proper Scrum posture. These steps can be easily implemented by an experienced coach.

For a novice ScrumMaster, failure to implement these steps will consistently incur the cost of poor velocity and quality. The results here can show the novice ScrumMaster which are the important features of Scrum that must be implemented to guarantee high performance. Novices will have to do their best to convince teams to follow best practices. For teams in this paper, the ScrumMasters had enough experience and management support to enforce the right practices and the leadership capability to get the teams to cooperate.

A. Lay the Foundation

Novice Leadership and Team Discovery approaches at MySpace and Jayway allowed the teams to become distracted by new terminology, roles and artifacts. In the absence of strong, experienced leadership, most teams spent their formative months focused on aspects of the framework rather than on delivering value to the customer. They also under-emphasized or failed to implement critical elements of the Scrum Framework, which sets them up for limited success at best.

These mistakes often led to a measurable initial reduction in value delivery rather than the expected increase that drove the decision to implement Scrum. To avoid this pitfall, the Shock Therapy coach, Scott Downey, fully enforced the complete Scrum Framework for teams described here. Scott found it was critical at the outset that the entire team participate in training so that everyone had the same

understanding of goals, mechanisms, definitions, and responsibilities they will share going forward. Teams in this study have participated in an internally developed Introduction to Scrum course that covers the Twelve Points of Scrum as well as the most impactful environmental factors of the MySpace technical and organizational structures. Until the Scrum Product Owner, Scrum Master, and entire Delivery Team participate in training, no further steps are taken to bootstrap that team.

B. Stabilize the Environment

The legitimate degrees of freedom in the Scrum Framework are often confused with Framework elements themselves. This can lead to accidental, dysfunctional hybrid models. Having a strong, experienced, and empowered coach is critical to getting teams functioning quickly and realizing the benefits of Scrum. To achieve this, the Shock Therapy Coaches at MySpace and Jayway take many of the legitimate degrees of freedom off the table by providing an additional but temporary structure that could be viewed as a “Default Profile” for new teams. Through practice and demonstrated proficiency, teams earn the right to change these Default Profile settings (but never the Scrum Framework).

Before changes in the Default Profile could be made, the teams in this study were required to complete three consecutive, successful Sprints, demonstrate a 240% increase in Velocity, and have a solid business reason to make a change that was agreed to by all team members.

Default Profile rules were applied consistently for the MySpace teams in this paper. At Jayway the same conceptual approach is used with minor variations.

  • Set Sprint Length The Shock Therapy Coach decides Sprint Length. Shorter Sprint lengths are recommended to facilitate more rapid inspect/adapt cycles. All teams in this study used one week Sprints.
  • Set the Definition of Done The Shock Therapy Coach provides an initial definition of Done that should be applicable to 80% of the work the team will pursue. Our initial definition of Done includes, at minimum:
    • Feature Complete
    • Code Complete
    • No Known Defects
    • Approved by the Scrum Product Owner
    • Production Ready

Although approval of delivered work is the domain of the Scrum Product Owner, during the Shock Therapy experience, the Coach must also agree that the work has met the agreed state of completion or s/he, too, can reject the work and direct it back to the Product Backlog.

  1. Strictly Filter User Stories – Only properly formed and supported User Stories are allowed into the Sprint by the Coach. Improperly formed Product Backlog content is rejected by the Coach on the team’s behalf before the Planning Meeting.
  2. Sprint Backlog Items – Sprint Backlog items are accepted at the highest level of granularity that passes the INVEST mnemonic [2]. At no point are cards broken into a list of tasks in pursuit of a task list alone.
  3. Only Estimate in Story Points – Estimation is in Story Points only. No estimates in Hours are ever solicited or tracked, and team members are discouraged from thinking of tasks in terms of time.
  4. A Physical Scrum Board Must Exist – A physical Information Radiator is designed by the Coach and serves as the focus of the daily 15-Minute Stand-Up Meeting. The simplest board with the minimum number of columns is recommended. Teams in this study used boards that displayed only Product Backlog, Sprint Backlog, Work In Progress, and Done. No “Waterfall” columns (e.g. Design, Dev, QA) were allowed. A physical board will be maintained even if software tools are used to provide visibility to remote locations.
  5. Respect for Team Meetings – A penalty for tardiness or unexpected absence from any team meeting is agreed to and enforced by the team. It applies equally to all team members, regardless of rank, role or excuses.
  6. The Sprint Planning Meeting will be 10% – the Sprint Planning Meeting will be 10% of the Sprint length in duration, and will include Sprint Review, Retrospective, Product Backlog Presentation, Estimation and Commitment of the Team.

C. Building Muscle Memory

During the Sprint, the Coach needs a singular focus on adherence to the Scrum Framework and Default Profile rules. It is best that s/he not be distracted by feelings of ownership over either the Product or the code. S/He must prevent multi-tasking, enforce working in priority order, encourage collaboration on the highest priority, and maintain the Scrum Board until the Team takes these things over, which usually happens naturally in the first several Sprints.

The Coach must constantly explain both rules and rationale used to derive advice or correction. As an example, when a lower priority card completes and the team member asks for more work, the Coach should not just advice, “Take the top item from the Product Backlog.” Rather, s/he should step them through the logic. “Can you help expedite any card that is already in progress? If not, can you work on any of the committed cards that are not yet started? If not, is there a better way to redistribute work across the team based on your availability right now? If not, retrieve the highest priority item from the Product Backlog and commit only to as much as can be completed by the end of the Sprint.”

It is important to engage the team in problem solving rather than always solving the problems yourself, as a Shock Therapy Coach. When the Coach notices someone multitasking, a team member not paying attention during the meeting, an Information Radiator that is not moving properly, or any other systemic or behavioral sub-optimizations, s/he should ask the team if they notice anything happening that should not be happening. Ask them to find and correct the defects and be available to help them if they begin to fail.

D. Seek Your Exit

At no point during Shock Therapy can the Coach become personally involved or vital to the team’s success beyond the bootstrapping experience. The Coach must not take on any fundamental tasks or fill in for any missing team members. It is critical to remember that the purpose of a Coach is to create self-sufficiency within the team. S/he must not become a foundational element of it and should seek to relinquish authority, leadership, and artifacts as soon as the team demonstrates an ability to absorb them.

Advertisements

Scrum in 10 minutes

Top 10 Project Management Trends for 2011

The top 10 Global Project Management Trends for 2011 include such key themes as building the project manager’s (PM) influence, accelerating new leadership and communication skills, and increased use of informal learning approaches such as social media and experiential training. A global panel of consultants and senior executives assembled by ESI identified the trends.

Leadership Skills Will Be the PM’s Critical Success Factor – Leadership skills, such as critical thinking, crucial communication and organizational change management, will be strategically imperative project management competencies to master. In 2011’s project management landscape – featuring more complex projects and greater use of virtual teams – being on time and on budget will require not just a laser-like focus on the triple constraints, but on the requisite leadership skills necessary for an individual PM’s success. The challenge for organizations will be to clearly define what “leadership” means in the project and program management context. 

No Industry Will Be Spared from the War for PM Talent – Savvy talent management and retention strategies will be essential to ward off poaching in 2011. Although economic recovery has been uneven worldwide, PMs with the greatest mobility and experience will have the best opportunities for career growth through “overseas” assignments. In particular, India and China will continue to be plagued by a dearth of competent and experienced PMs to manage large and complex infrastructure and IT projects. Additionally, as mega-projects at the King Abdullah Economic City north of Jeddah and King Abdullah Financial District on the outskirts of Riyadh kick into high gear, more opportunities for work in the Middle East will become a reality.

Agile Will Be Seen for What It Is…and Isn’t – Project management organizations embracing Agile software and product development approaches will continue to grow while being faced with the challenge of demonstrating ROI through Agile adoption. In addition, they will need to disabuse their stakeholders and executives of the expectations set by IT consultants, the media and the vendor community that Agile is the next “silver bullet.” Organizations that do it right – including selecting the right projects for Agile – will reap significant rewards.

Competency Models Will Be Core to Managing Professional Development and Promotions for PMs – As project management gains greater acceptance as a discipline, the hiring, assignment, promotion and professional development of PMs will be based on comprehensive competency models. In order for these models to be effective, they must be company-specific. Competency models illuminate the behaviors required for a PM to be successful and take on larger and more complex projects. Accordingly, the CLO (or senior HR executive), business unit heads and the enterprise project management office (EPMO) need to work shoulder-to-shoulder to identify and codify organization-specific competencies, thereby building a framework for talent management success.

Experiential Learning Will Be More the Norm than the Exception – The professional development of PMs will increasingly focus on reality-based learning and on-the-job training, an approach certain organizations in Asia have taken for many years. Learning providers will be required to send PMs back to the job from such sessions with the ability to immediately apply what they learned to their current projects. Even the many universities that offer project management degrees will face the challenge of making their courses and programs relevant, practical and pragmatic based on participants’ real projects. The lecture mode is dead and any training provider or university who ignores it does so at its peril.

Informal Learning for PMs Will Gain Momentum – Organizations will continue to develop and exploit informal learning approaches such as communities of practice (CoP), various forms of social media, as well as coaching and mentoring. With millennials joining the workforce in greater numbers, we will witness more effective use of social learning technologies and approaches, such as wikis, blogs, videos, podcasts and other methods of communication. With four generations now in the workplace, it is not only the millennials who will benefit by such relatively new forms of learning. However, the great Zen kōan question of the day is, “If informal learning becomes formal, does it become formal learning?” If the answer is yes, do we search for more informal learning to formalize?

Project Sponsorship Will Become an Area of Focus in South Asia – The roles and responsibilities of the project sponsor will be a key focus in South Asia, especially in India and Bangladesh, as organizations try to accelerate their structured approach to project management. Such organizations are trying to avoid the experience of others in their industries around the world whose “spotty” record of success in project sponsorship has contributed in whole, or in part, to less than successful projects.

Outsourcing Will Remain a Risky Business – The continued growth of outsourcing will force organizations to pay more heed to its associated risks and conduct better due diligence. As a response, organizations will strengthen their risk management cultures and recognize the value of best practices in contract management. More than a euphemism, the word “sourcing” will replace the term outsourcing as it more accurately describes the resource allocation approach both internally and externally for many organizations.

PMs Will Team with “Change Partners” and Use Structured Methods to Facilitate Adoption – Projects initiate change and PMs are change agents. Yet, they have been ill-equipped to facilitate the type of change required to adopt the product or service the project delivers. In 2011, we will see more organizations developing and assigning “change partners,” also known as change management experts, to projects to assist in such adoption. Moreover, project teams will slowly, but steadily, increase their use of change management methods, which will be packaged as methodologies.

The PMP® Will Continue its “World Domination,” but Will No Longer Be Enough

– With 400,000+ holders, the PMP® will continue to be the most popular project management credential in the world, outpacing every one of its rivals as the “credential of choice” among practitioners. While most organizations will continue to support their PMs in earning the credential, the value of proven experience and demonstrated competency will take on even more relevance beyond having the certification itself.

The author J. LeRoy Ward, PMP, PgMP is the Executive Vice President, ESI.

Standup Meetings

Implementing standup meetings or in scrum – daily scrum meetings should be not be too serious about the roles of its participants in the chicken and pig roles because if your team falls under this misconception then you become a slave of the concept.

Remember collaboration is a key.

The Scrum Master should be master of your of interaction – he/she must be sensitive and listen to his team.

The team should know what to do after each daily scrum meetings. PDCA is key – Plan/Do/Check/Act.

Macro Management in SCRUM

Still I cannot get over it…. yesterday I was able to finish the training for SCRUM Master but it just keep rubbing in.  It seems that the trainors of SCRUM is saying to me that SCRUM is the only methodology that practices MACRO Management in a project.

If in any case you are a project manager in any industry may it be IT, Software, Hardware, Construction, etc…. this is a trait of a good project manager if one would macro manage and still knows what is being done by your teammates.  A good project manager is not just command and control but he listens a lot.

I have been in the IT industry for quite some time now and I believe that a PM or any lead should have the following traits:

  • A good listener
  • is Proactive
  • inspire a shared vision
  • provides Win-Win Solution
  • has the trait of a problem solver
  • has team building skills
  • can influence people even if he has no title
  • has the ability to delegate tasks
  • is cool under pressure
  • has self-mastery on what he/she do
  • has integrity
  • and a good communicator

CSM Training

I am now a Certified Scrum Master…… but I don’t feel to be a master 😦

I think the concepts was presented well but it seems that I have an impression that people who are doing scrum are rebellious in a sense.  One of the trainors (Bas Vodde) who I assume is  leader in the SCRUM community for me is purist in a sense.

Personally I think the training of CSM should be attended by Project Managers, Lead Developers, Business Analyst and Managers but most of the people who attended the training were developers who do not have any experience in leading a team so I think it is very dangerous for this people to attend this kind of trainings because in implementing scrum one should have a concepts of managing and leading a team.

The concept of SCRUM is so simple yet so hard to implement.

Bas Vodde, one of trainors who I would label as a purist in SCRUM and a SCRUM coach in my own personal opinion lacks the maturity be one.  Maybe, I am too direct in my choice of words but during the Q&A for the CSM training he was dodging every question of the class and could not answer most of questions in a manner that a mentor or a coach should be answering.

He said “keep the Project Manager out of the picture when you are implementing scrum“.  He is adamant in saying that project management is not a good idea but SCRUM is distributing the function and roles of Project Management in the Product Owner and the Scrum Master.

When a coach would say that he don’t see any need for an audit or a process and to keep management away I feel that concepts of the coaches mind is distorted.  SCRUM in itself is a process of delivering a project while audits is still needed because any customer-vendor relationship would want to have a snapshot what is happening on a project and management would always be there because they are the ones who paying the delivery team.

This is so sad to hear from an author, mentor and even as a SCRUM coach.