Many Project Managers come to my courses to find out whether Scrum and Agile are something for them and their for organizations. Sometimes the answer regarding Scrum is ‘No.’ What then? What can you do with the lessons of Scrum to improve your productivity if you’re constrained to phase driven development? This is where the values of the Agile Manifesto can be really helpful!
Yvonne Horst, a Project Leader for Swisscom and recent CSM, just sent me a nice example (she also sent a nice recommendation for my course, but I digress):
“I would like to point out one idea. The usual staffing approach for projects in a non-Scrum environment is to send specialists into a project and have them produce the artifacts of the respective phase. At the end of the phase the artifacts are handed over to the next group of specialists, which makes it sometimes extremely difficult to ensure the know-how transfer over the whole lifespan of the project.
“The idea of the Scrum team with all necessary skills on board to solve whatever problem that may occur can be transferred into a waterfall team as well – if only by booking one or two key resources over the whole lifespan of the project.
“I want to go one step further now and am currently building a team of requirements engineering specialists, each and every one of them with in depth know-how of at least one core system. They will no longer be sent to projects, but the projects may in future obtain results from this team for their specific problem/changes/challenges/high level requirements with reference to the represented core systems. The team works and acts together.
“The first feedback from the business units as well as the Project Managers has been enthusiastic. And the team members tell me that they have learned more from their colleagues in the last two weeks than in the two years before…”
Here we have an example of applying both a Scrum practice and the Agile value, “People and Interactions”. You can apply the Manifesto for Agile Software Development to any context. You do not have to do Scrum or XP to be Agile! Just value the “stuff on the left” more in your decision making:
What are you already doing that values Individuals and Interactions or Working Software? What could you do more of (or less of) to emphasize these values? What could you start doing?
And Scrum itself can provide the inspiration for possible improvements. How could you apply timeboxing? How could you inspect and adapt more frequently on the basis of honest information?
I am sure there are other examples of applying Agile Values and Scrum Practices to traditional project management. I’d love to hear your suggestions and examples!
|cookielawinfo-checkbox-advertisement||1 year||Set by the GDPR Cookie Consent plugin, this cookie is used to record the user consent for the cookies in the "Advertisement" category .|
|cookielawinfo-checkbox-analytics||11 months||This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics".|
|cookielawinfo-checkbox-functional||11 months||The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional".|
|cookielawinfo-checkbox-necessary||11 months||This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary".|
|cookielawinfo-checkbox-others||11 months||This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other.|
|cookielawinfo-checkbox-performance||11 months||This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance".|
|mailchimp_landing_site||1 month||The cookie is set by MailChimp to record which page the user first visited.|
|CONSENT||2 years||YouTube sets this cookie via embedded youtube-videos and registers anonymous statistical data.|
|_ga||2 years||The _ga cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognize unique visitors.|
|_gat_gtag_UA_42152348_1||1 minute||Set by Google to distinguish users.|
|_gcl_au||3 months||Provided by Google Tag Manager to experiment advertisement efficiency of websites using their services.|
|_gid||1 day||Installed by Google Analytics, _gid cookie stores information on how visitors use a website, while also creating an analytics report of the website's performance. Some of the data that are collected include the number of visitors, their source, and the pages they visit anonymously.|
|NID||6 months||NID cookie, set by Google, is used for advertising purposes; to limit the number of times the user sees an ad, to mute unwanted ads, and to measure the effectiveness of ads.|
|test_cookie||15 minutes||The test_cookie is set by doubleclick.net and is used to determine if the user's browser supports cookies.|
|VISITOR_INFO1_LIVE||5 months 27 days||A cookie set by YouTube to measure bandwidth that determines whether the user gets the new or old player interface.|
|YSC||session||YSC cookie is set by Youtube and is used to track the views of embedded videos on Youtube pages.|
|yt-remote-connected-devices||never||YouTube sets this cookie to store the video preferences of the user using embedded YouTube video.|
|yt-remote-device-id||never||YouTube sets this cookie to store the video preferences of the user using embedded YouTube video.|
|COMPASS||1 hour||No description|
|cookies.js||session||No description available.|
|S||1 hour||No description available.|
Agile scrum has its own particular philosophy and working. It is unique as a framework. I guess if Agile practices and principles are implemented in a waterfall project, even on a marginal level, would waterfall remain as waterfall? Or, would be a pseudo version of Waterfall-Agile hybrid? The question would be to be really Agile or a “Scrumbut”?
Hi Scrum Tool,
I think you can be Agile without replacing you Gantt charts with a burn down chart. Start applying the Agile values. What do we do now that values, say, working software over extensive documentation? What could we change, so that we can become more aligned with valuing working software? It's a small steps approach.
I think in this case, the big mindshift is saying, we want to get better, so let's look for better ways of developing software.