Out of curiosity, do Bookings staff members actively work on the Perl 5 C sources?
Or do they just fund Perl development?
To further clarify, the main point of my scenario was to ponder whether employees
of such a mythical company, working in Scrum cross-functional teams with a goal of
producing "customer value", would be eager to work on the Perl 5 C code
or whether they would try to avoid doing that and instead focus on writing
new Perl 5 systems to provide "better customer value at a higher velocity"
(and so get to drive a new BMW and park in one of the fancy spots:-).
In this mythical scenario, the customer does not know or care about Perl,
they just want their systems delivered on time that satisfy their needs.
Perl is mimicking the closed-source "infrastructure or core component"
that caused so many headaches for Schwaber
when implementing Scrum in cross-functional teams that are meant to be self
sufficient; that is, each team is meant to be capable of
maintaining the Perl C sources.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|