Thoughts on the Developer Open Assessment

Hi Fredrik,

Thank you for your message. Work is underway to publish a Book of Knowledge list for the Developer Open and general Scrum Developer knowledge on Scrum.org. An announcement will be made via our twitter feed within the next week or so.

Best,
Daniel

Hello, I'm new here, but not new to SCRUM. I just took the Developer Open (that's what I primarily do), and in reviewing my result, I have some thoughts about one of the questions that I got:

The question was: "What are ways a Development Team can ensure a good application architecture?" with the following options as responses (only selecting 2)

1. The Development Team plans a Sprint 0 at the beginning of a project with the objective of developing an architecture model used during the following Sprints.

2. A Development Team doesn't need an architecture model in Scrum and should focus on adding functionality. The architecture will come into place without fail as the Development Team adds functionality.

3. The Development Team should have a set of guiding architecture principles that every Development Team member understands and follows when writing code.

4. The Development Team should assign someone to the role of software architect whose job it is to make sure a consistent architecture is developed.

5. The Development Team plans some time each Sprint to discuss the architecture needed for the features planned in that Sprint.

I selected items 1, and 5, because there needs to be a consensus on HOW a Software Solution will be implemented, and that consensus MUST include the Business side of the house. 

The response that I got back was that the correct items were 3 and 5, with the following feedback:

Feedback

"There is no specific "architect" role on a Scrum team, nor is there an architecture planning Sprint.  But, a good architecture doesn't just happen automatically.  Guiding principles and frequent conversations on the team help ensure that the most appropriate architecture is developed as it is needed by features being developed in the current Sprint"

My question:

The way I understand it, SCRUM states that the Development Team is a cross-functional group that supports a given software product, or suite of products. If that is true, then even though there is no "architect" role, the Development Team has members on it that do not function as software developers. Therefore Item #3 is disqualified, because it implies that all members of the Development team are Software Developers, and it is only these people who write code. 

The Development Team plans a Sprint 0 at the beginning of a project

This answer is incorrect, since there is no Sprint Zero in Scrum (reminiscent of BPUF - Big Planning Up Front).   Therefore, #1 cannot be true.

#4 is also false, since it attempts to silo an individual on the Development Team.

Since Scrum and Agile embrace an architectural approach that evolves as functionality is delivered, I can see #2, #3, and #5 as possible answers.   However, #2 implies that the architecture will "just happen", whereas #3 and #5 provide an intentional, practical approach to architecture development.

So the correct answers are #3 and #5.

Ok, I get where #5 is correct. But how does #3 pass muster when it specifically speaks to only one function of the team? Most BA's don't regularly cut code. Test might do some, but the Business User? I'm having trouble seeing it, the way the option is worded.

The Development Team should have a set of guiding architecture principles that every Development Team member understands and follows when writing code.

It does state 'when writing code', which to me makes it 3 correct.

Ok, I get where #5 is correct. But how does #3 pass muster when it specifically speaks to only one function of the team? Most BA's don't regularly cut code. Test might do some, but the Business User? I'm having trouble seeing it, the way the option is worded.

Do you think a good Scrum Development team ought to have functions that inhibit collaboration?

From my perspective, the term "cross-functional" is exactly that. The Development Team is composed of individuals that, at the very least, understand what the results are supposed to be, what inputs are required,  and how the transformation works. There's no code required for that level of understanding and/or consensus.

It's THAT kind of communication that makes SCRUM work. Anything short of that will have issues.

Most BA's don't regularly cut code. Test might do some, but the Business User? 

Andrew, are any of these Scrum roles?   

Do you think considering individual skills within the Development Team for option #3 might be one reason why you're questioning the answer?